Re: [Openstack] Problems with drbd + pacemaker in HA

[Sébastien Han]

Hi,

If you stop the resource this is perfectly normal to get a resource
diskless and unconfigured since you asked pacemaker to stop it. You just
need to reconnect properly the resource 0 (guess it's the mysql one). For
this, it's more or less the same operation as this one:
http://www.drbd.org/users-guide-8.3/s-resolve-split-brain.html

Cheers

--
Regards,
Sébastien Han.


On Tue, Feb 19, 2013 at 2:38 AM, Samuel Winchenbach wrote:

> Hi All,
>
> I recently switched from CentOS 6.3 to Ubuntu LTS server and have started
> encountering some really odd problems with drbd and pacemaker.   everything
> seems to work well until I stop a resource or migrate itl at which point
> drbd either becomes "Diskless" or "Unconfigured".  I am not sure what is
> happening but I never had this problem in CentOS.
>
> pacemaker configuration:  http://paste2.org/p/2905943
> drbd configuration: http://paste2.org/p/2905965
>
> syslog output: http://paste2.org/p/2905988
> drbd state problems: http://paste2.org/p/2905951
>
>
> If someone could take a quick look at this I would be very grateful, I
> have been fighting this for a couple days now.
>
> Thanks,
> Sam
>
>
> ___
> 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] HA Openstack with Pacemaker

[Sébastien Han]

Well if you follow my article, you will get LVS-NAT running. It's fairly
easy, no funky stuff. Yes you will probably need the postrouting rule, as
usual :). Let me know how it goes ;)

--
Regards,
Sébastien Han.


On Fri, Feb 15, 2013 at 8:51 PM, Samuel Winchenbach wrote:

> I
> didn't give NAT a shot because it didn't seem as well documented.
>
> I will give NAT a shot.  Will I need to enable to iptables and add a rule
> to the nat table?   None of the documentation mentioned that but every time
> I have ever done NAT I had to setup a rule like... iptables -t nat -A
> POSTROUTING -o eth0 -j MASQUERADE
>
> Thanks for helping me with this.
>
>
> On Fri, Feb 15, 2013 at 2:07 PM, Sébastien Han wrote:
>
>> Ok but why direct routing instead of NAT? If the public IPs are _only_
>> on LVS there is no point to use LVS-DR.
>>
>> LVS has the public IPs and redirects to the private IPs, this _must_ work.
>>
>> Did you try NAT? Or at least can you give it a shot?
>> --
>> Regards,
>> Sébastien Han.
>>
>>
>> On Fri, Feb 15, 2013 at 3:55 PM, Samuel Winchenbach 
>> wrote:
>> > Sure...  I have undone these settings but I saved a copy:
>> >
>> > two hosts:
>> > test1 eth0: 10.21.0.1/16 eth1: 130.x.x.x/24
>> > test2 eth0: 10.21.0.2/16 eth1: 130.x.x.x/24
>> >
>> > VIP: 10.21.21.1  (just for testing, later I would add a 130.x.x.x/24
>> VIP for
>> > public APIs
>> >
>> > k
>> > eystone is bound to 10.21.0.1 on test1 and 10.21.0.2 on test2
>> >
>> >
>> >
>> > in /etc/sysctl.conf:
>> >net.ipv4.conf.all.arp_ignore = 1
>> >net.ipv4.conf.eth0.arp_ignore = 1
>> >net.ipv4.conf.all.arp_announce = 2
>> >net.ipv4.conf.eth0.arp_announce = 2
>> >
>> > root# sysctl -p
>> >
>> > in /etc/sysctl.conf:
>> >
>> > checktimeout=
>> > 3
>> >
>> >
>> > checkinterval=
>> > 5
>> >
>> >
>> > autoreload=
>> > yes
>> >
>> >
>> > logfile="/var/log/ldirectord.log"
>> >
>> > quiescent=no
>> >
>> > virtual=10.21.21.1:5000
>> >
>> > real=10.2
>> > 1
>> > .0.1:5000 gate
>> >
>> > real=10.2
>> > 1
>> > .0.2:5000 gate
>> >
>> > scheduler=
>> > w
>> > rr
>> >   protocol=tcp
>> >   checktype=connect
>> >   checkport=5000
>> >
>> > virtual=10.21.21.1:
>> > 35357
>> >
>> > real=10.2
>> > 1
>> > .0.1:
>> > 35357
>> > gate
>> >
>> > real=10.2
>> > 1
>> > .0.2:
>> > 35357
>> > gate
>> >
>> > scheduler=
>> > w
>> > rr
>> >   protocol=tcp
>> >   checktype=connect
>> >   checkport=35357
>> >
>> >
>> > crm shell:
>> >
>> >
>> > primitive
>> > p_openstack_
>> > ip ocf:heartbeat:IPaddr2 \
>> >
>> >
>> > op monitor interval="60" timeout="20" \
>> >
>> >
>> > params ip=
>> > "10.21.21.1
>> > "
>> > cidr_netmask="
>> > 16
>> > "
>> > lvs_support="true"
>> >
>> > p
>> > rimitive
>> > p_openstack_ip_lo
>> >  ocf:heartbeat:IPaddr2 \
>> >
>> >
>> > op monitor interval="60" timeout="20" \
>> >
>> >
>> > params ip="
>> > 10.21.21.1
>> > " nic="lo"
>> > cidr_netmask="32"
>> >
>> > primitive
>> > p_openstack_
>> > lvs ocf:heartbeat:ldirectord \
>> >
>> >
>> > op monitor interval="20" timeout="10"
>> >
>> > group
>> > g_openstack_
>> > ip
>> > _
>> > lvs
>> > p_openstack_
>> > ip
>> > p_openstack_
>> > lvs
>> >
>> > clone
>> > c_openstack_ip_lo
>> >
>> > p_openstack_ip_lo
>> > meta interleave="true"
>> >
>> > colocation
>> > co_openstack_lo_never_lvs
>> > -inf: c
>> > _openstack_ip_lo
>> >
>> > g_openstack_ip_lvs
>> >
>> > Thanks for taking a look at this.
>> >
>> > Sam
>> >

Re: [Openstack] Suggestions for shared-storage cluster file system

[Sébastien Han]

Hi,

Important: Mount the CephFS filesystem on the client machine, not the
> cluster machine.


It's just like NFS, if you mount an NFS export on the NFS server, you get
kernel locks.

Unfortunately even if love Ceph far more than the other, I won't go with
CephFS, at least not know. But if are in a hurry and looking for a DFS then
GlusterFS seems to be a good candidate. NFS works pretty well too.

Cheers.

--
Regards,
Sébastien Han.


On Fri, Feb 15, 2013 at 4:49 PM, JuanFra Rodriguez Cardoso <
juanfra.rodriguez.card...@gmail.com> wrote:

> Another one:
>
>  - MooseFS (
> http://docs.openstack.org/trunk/openstack-compute/admin/content/installing-moosefs-as-backend.html
> )
>  - GlusterFS
>  - Ceph
>  - Lustre
>
> Regards,
> JuanFra
>
>
> 2013/2/15 Samuel Winchenbach 
>
>>  Hi All,
>>
>> Can anyone give me a recommendation for a good shared-storage cluster
>> filesystem?   I am running kvm-libvirt and would like to enable live
>> migration.
>>
>> I have a number of hosts (up to 16) each with 2xTB drives.  These hosts
>> are also my compute/network/controller nodes.
>>
>> The three I am considering are:
>>
>> GlusterFS - I have the most experience with this, and it seems the
>> easiest.
>>
>> CephFS/RADOS - Interesting because glance supports the rbd backend.
>>  Slightly worried because of this though "Important:
>> Mount the CephFS filesystem on the client machine, not the cluster
>> machine."
>> (I wish it said why...)  and "CephFS is not quite as stable as the block
>> device and the object storage gateway."
>>  Lustre - A little hesitant now that Oracle is involved with it.
>>
>>
>> If anyone has any advice, or can point out another that I should consider
>> it would be greatly appreciated.
>>
>> Thanks!
>>
>> Sam
>>
>>
>> ___
>> 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] HA Openstack with Pacemaker

[Sébastien Han]

Ok but why direct routing instead of NAT? If the public IPs are _only_
on LVS there is no point to use LVS-DR.

LVS has the public IPs and redirects to the private IPs, this _must_ work.

Did you try NAT? Or at least can you give it a shot?
--
Regards,
Sébastien Han.


On Fri, Feb 15, 2013 at 3:55 PM, Samuel Winchenbach  wrote:
> Sure...  I have undone these settings but I saved a copy:
>
> two hosts:
> test1 eth0: 10.21.0.1/16 eth1: 130.x.x.x/24
> test2 eth0: 10.21.0.2/16 eth1: 130.x.x.x/24
>
> VIP: 10.21.21.1  (just for testing, later I would add a 130.x.x.x/24 VIP for
> public APIs
>
> k
> eystone is bound to 10.21.0.1 on test1 and 10.21.0.2 on test2
>
>
>
> in /etc/sysctl.conf:
>net.ipv4.conf.all.arp_ignore = 1
>net.ipv4.conf.eth0.arp_ignore = 1
>net.ipv4.conf.all.arp_announce = 2
>net.ipv4.conf.eth0.arp_announce = 2
>
> root# sysctl -p
>
> in /etc/sysctl.conf:
>
> checktimeout=
> 3
>
>
> checkinterval=
> 5
>
>
> autoreload=
> yes
>
>
> logfile="/var/log/ldirectord.log"
>
> quiescent=no
>
> virtual=10.21.21.1:5000
>
> real=10.2
> 1
> .0.1:5000 gate
>
> real=10.2
> 1
> .0.2:5000 gate
>
> scheduler=
> w
> rr
>   protocol=tcp
>   checktype=connect
>   checkport=5000
>
> virtual=10.21.21.1:
> 35357
>
> real=10.2
> 1
> .0.1:
> 35357
> gate
>
> real=10.2
> 1
> .0.2:
> 35357
> gate
>
> scheduler=
> w
> rr
>   protocol=tcp
>   checktype=connect
>   checkport=35357
>
>
> crm shell:
>
>
> primitive
> p_openstack_
> ip ocf:heartbeat:IPaddr2 \
>
>
> op monitor interval="60" timeout="20" \
>
>
> params ip=
> "10.21.21.1
> "
> cidr_netmask="
> 16
> "
> lvs_support="true"
>
> p
> rimitive
> p_openstack_ip_lo
>  ocf:heartbeat:IPaddr2 \
>
>
> op monitor interval="60" timeout="20" \
>
>
> params ip="
> 10.21.21.1
> " nic="lo"
> cidr_netmask="32"
>
> primitive
> p_openstack_
> lvs ocf:heartbeat:ldirectord \
>
>
> op monitor interval="20" timeout="10"
>
> group
> g_openstack_
> ip
> _
> lvs
> p_openstack_
> ip
> p_openstack_
> lvs
>
> clone
> c_openstack_ip_lo
>
> p_openstack_ip_lo
> meta interleave="true"
>
> colocation
> co_openstack_lo_never_lvs
> -inf: c
> _openstack_ip_lo
>
> g_openstack_ip_lvs
>
> Thanks for taking a look at this.
>
> Sam
>
>
>
>
> On Fri, Feb 15, 2013 at 3:54 AM, Sébastien Han 
> wrote:
>>
>> Hum I don't see the problem, it's possible to load-balance VIPs with LVS,
>> there are just IPs... Can I see your conf?
>>
>> --
>> Regards,
>> Sébastien Han.
>>
>>
>> On Thu, Feb 14, 2013 at 8:34 PM, Samuel Winchenbach 
>> wrote:
>>>
>>> W
>>> ell, I think I will have to go with one ip per service and forget about
>>> load balancing.  It seems as though with LVS routing requests internally
>>> through the VIP is difficult (impossible?) at least with LVS-DR.  It seems
>>> like a shame not to be able to distribute the work among the controller
>>> nodes.
>>>
>>>
>>> On Thu, Feb 14, 2013 at 9:50 AM, Samuel Winchenbach 
>>> wrote:
>>>>
>>>> Hi Sébastien,
>>>>
>>>> I have two hosts with public interfaces with a number (~8) compute nodes
>>>> behind them.   I am trying to set the two public nodes in for HA and load
>>>> balancing,  I plan to run all the openstack services on these two nodes in
>>>> Active/Active where possible.   I currently have MySQL and RabbitMQ setup 
>>>> in
>>>> pacemaker with a drbd backend.
>>>>
>>>> That is a quick summary.   If there is anything else I can answer about
>>>> my setup please let me know.
>>>>
>>>> Thanks,
>>>> Sam
>>>>
>>>>
>>>> On Thu, Feb 14, 2013 at 9:26 AM, Sébastien Han 
>>>> wrote:
>>>>>
>>>>> Well I don't know your setup, if you use LB for API service or if you
>>>>> use an active/passive pacemaker but at the end it's not that much IPs I
>>>>> guess. I dare to say that Keepalived sounds outdated to me...
>>>>>
>>>>> If you use pacemaker and want to have the same IP for all the resources
>>>>> simply create a resource group

Re: [Openstack] HA Openstack with Pacemaker

[Sébastien Han]

Hum I don't see the problem, it's possible to load-balance VIPs with LVS,
there are just IPs... Can I see your conf?

--
Regards,
Sébastien Han.


On Thu, Feb 14, 2013 at 8:34 PM, Samuel Winchenbach wrote:

> W
> ell, I think I will have to go with one ip per service and forget about
> load balancing.  It seems as though with LVS routing requests internally
> through the VIP is difficult (impossible?) at least with LVS-DR.  It seems
> like a shame not to be able to distribute the work among the controller
> nodes.
>
>
> On Thu, Feb 14, 2013 at 9:50 AM, Samuel Winchenbach wrote:
>
>> Hi Sébastien,
>>
>> I have two hosts with public interfaces with a number (~8) compute nodes
>> behind them.   I am trying to set the two public nodes in for HA and load
>> balancing,  I plan to run all the openstack services on these two nodes in
>> Active/Active where possible.   I currently have MySQL and RabbitMQ setup
>> in pacemaker with a drbd backend.
>>
>> That is a quick summary.   If there is anything else I can answer about
>> my setup please let me know.
>>
>> Thanks,
>> Sam
>>
>>
>> On Thu, Feb 14, 2013 at 9:26 AM, Sébastien Han 
>> wrote:
>>
>>> Well I don't know your setup, if you use LB for API service or if you
>>> use an active/passive pacemaker but at the end it's not that much IPs I
>>> guess. I dare to say that Keepalived sounds outdated to me...
>>>
>>> If you use pacemaker and want to have the same IP for all the resources
>>> simply create a resource group with all the openstack service inside it
>>> (it's ugly but if it's what you want :)). Give me more info about your
>>> setup and we can go further in the discussion :).
>>>
>>> --
>>> Regards,
>>> Sébastien Han.
>>>
>>>
>>> On Thu, Feb 14, 2013 at 3:15 PM, Samuel Winchenbach 
>>> wrote:
>>>
>>>> T
>>>> he only real problem is that it would consume a lot of IP addresses
>>>> when exposing the public interfaces.   I _think_ I may have the solution in
>>>> your blog actually:
>>>> http://www.sebastien-han.fr/blog/2012/10/19/highly-available-lvs/
>>>> and
>>>> http://clusterlabs.org/wiki/Using_ldirectord
>>>>
>>>> I am trying to weigh the pros and cons of this method vs
>>>> keepalived/haproxy and just biting the bullet and using one IP per service.
>>>>
>>>>
>>>> On Thu, Feb 14, 2013 at 4:17 AM, Sébastien Han >>> > wrote:
>>>>
>>>>> What's the problem to have one IP on service pool basis?
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Sébastien Han.
>>>>>
>>>>>
>>>>> On Wed, Feb 13, 2013 at 8:45 PM, Samuel Winchenbach <
>>>>> swinc...@gmail.com> wrote:
>>>>>
>>>>>> What if the VIP is created on a different host than keystone is
>>>>>> started on?   It seems like you either need to set 
>>>>>> net.ipv4.ip_nonlocal_bind
>>>>>> = 1 or create a colocation in pacemaker (which would either require all
>>>>>> services to be on the same host, or have an ip-per-service).
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Feb 13, 2013 at 2:28 PM, Razique Mahroua <
>>>>>> razique.mahr...@gmail.com> wrote:
>>>>>>
>>>>>>> There we go
>>>>>>> https://review.openstack.org/#/c/21581/
>>>>>>>
>>>>>>> *Razique Mahroua** - **Nuage & Co*
>>>>>>> razique.mahr...@gmail.com
>>>>>>> Tel : +33 9 72 37 94 15
>>>>>>>
>>>>>>>
>>>>>>> Le 13 févr. 2013 à 20:15, Razique Mahroua 
>>>>>>> a écrit :
>>>>>>>
>>>>>>> I'm currently updating that part of the documentation - indeed it
>>>>>>> states that two IPs are used, but in fact, you end up with only one VIP 
>>>>>>> for
>>>>>>> the API service.
>>>>>>> I'll send the patch tonight
>>>>>>>
>>>>>>> *Razique Mahroua** - **Nuage & Co*
>>>>>>> razique.mahr...@gmail.com
>>>>>>> Tel : +33 9 72 37 94 15
>>>>>>>
>>>>>>&g

Re: [Openstack] HA Openstack with Pacemaker

[Sébastien Han]

Well I don't know your setup, if you use LB for API service or if you use
an active/passive pacemaker but at the end it's not that much IPs I guess.
I dare to say that Keepalived sounds outdated to me...

If you use pacemaker and want to have the same IP for all the resources
simply create a resource group with all the openstack service inside it
(it's ugly but if it's what you want :)). Give me more info about your
setup and we can go further in the discussion :).

--
Regards,
Sébastien Han.


On Thu, Feb 14, 2013 at 3:15 PM, Samuel Winchenbach wrote:

> T
> he only real problem is that it would consume a lot of IP addresses when
> exposing the public interfaces.   I _think_ I may have the solution in your
> blog actually:
> http://www.sebastien-han.fr/blog/2012/10/19/highly-available-lvs/
> and
> http://clusterlabs.org/wiki/Using_ldirectord
>
> I am trying to weigh the pros and cons of this method vs
> keepalived/haproxy and just biting the bullet and using one IP per service.
>
>
> On Thu, Feb 14, 2013 at 4:17 AM, Sébastien Han wrote:
>
>> What's the problem to have one IP on service pool basis?
>>
>> --
>> Regards,
>> Sébastien Han.
>>
>>
>> On Wed, Feb 13, 2013 at 8:45 PM, Samuel Winchenbach 
>> wrote:
>>
>>> What if the VIP is created on a different host than keystone is started
>>> on?   It seems like you either need to set net.ipv4.ip_nonlocal_bind =
>>> 1 or create a colocation in pacemaker (which would either require all
>>> services to be on the same host, or have an ip-per-service).
>>>
>>>
>>>
>>>
>>> On Wed, Feb 13, 2013 at 2:28 PM, Razique Mahroua <
>>> razique.mahr...@gmail.com> wrote:
>>>
>>>> There we go
>>>> https://review.openstack.org/#/c/21581/
>>>>
>>>> *Razique Mahroua** - **Nuage & Co*
>>>> razique.mahr...@gmail.com
>>>> Tel : +33 9 72 37 94 15
>>>>
>>>>
>>>> Le 13 févr. 2013 à 20:15, Razique Mahroua 
>>>> a écrit :
>>>>
>>>> I'm currently updating that part of the documentation - indeed it
>>>> states that two IPs are used, but in fact, you end up with only one VIP for
>>>> the API service.
>>>> I'll send the patch tonight
>>>>
>>>> *Razique Mahroua** - **Nuage & Co*
>>>> razique.mahr...@gmail.com
>>>> Tel : +33 9 72 37 94 15
>>>>
>>>> 
>>>>
>>>> Le 13 févr. 2013 à 20:05, Samuel Winchenbach  a
>>>> écrit :
>>>>
>>>> In that documentation it looks like each openstack service gets it own
>>>> IP (keystone is being assigned 192.168.42.103 and glance is getting
>>>> 192.168.42.104).
>>>>
>>>> I might be missing something too because in the section titled
>>>> "Configure the VIP" it create a primitive called "p_api-ip" (or p_ip_api if
>>>> you read the text above it) and then in "Adding Keystone resource to
>>>> Pacemaker" it creates a group with "p_ip_keystone"???
>>>>
>>>>
>>>> Stranger yet, "Configuring OpenStack Services to use High Available
>>>> Glance API" says:  "For Nova, for example, if your Glance API service
>>>> IP address is 192.168.42.104 as in the configuration explained here, you
>>>> would use the following line in your nova.conf file : glance_api_servers
>>>> = 192.168.42.103"  But, in the step before it set:  "registry_host =
>>>> 192.168.42.104"?
>>>>
>>>> So I am not sure which ip you would connect to here...
>>>>
>>>> Sam
>>>>
>>>>
>>>>
>>>> On Wed, Feb 13, 2013 at 1:29 PM, JuanFra Rodriguez Cardoso <
>>>> juanfra.rodriguez.card...@gmail.com> wrote:
>>>>
>>>>> Hi Samuel:
>>>>>
>>>>> Yes, it's possible with pacemaker. Look at
>>>>> http://docs.openstack.org/trunk/openstack-ha/content/ch-intro.html.
>>>>>
>>>>> Regards,
>>>>> JuanFra
>>>>>
>>>>>
>>>>> 2013/2/13 Samuel Winchenbach 
>>>>>
>>>>>>  Hi All,
>>>>>>
>>>>>> I currently have a HA OpenStack cluster running where the OpenStack
>>>>>> services are kept alive with a combination of haproxy and keepalived.
>>>>>>
>>>>>>

Re: [Openstack] HA Openstack with Pacemaker

[Sébastien Han]

What's the problem to have one IP on service pool basis?

--
Regards,
Sébastien Han.


On Wed, Feb 13, 2013 at 8:45 PM, Samuel Winchenbach wrote:

> What if the VIP is created on a different host than keystone is started
> on?   It seems like you either need to set net.ipv4.ip_nonlocal_bind = 1
> or create a colocation in pacemaker (which would either require all
> services to be on the same host, or have an ip-per-service).
>
>
>
>
> On Wed, Feb 13, 2013 at 2:28 PM, Razique Mahroua <
> razique.mahr...@gmail.com> wrote:
>
>> There we go
>> https://review.openstack.org/#/c/21581/
>>
>> *Razique Mahroua** - **Nuage & Co*
>> razique.mahr...@gmail.com
>> Tel : +33 9 72 37 94 15
>>
>>
>> Le 13 févr. 2013 à 20:15, Razique Mahroua  a
>> écrit :
>>
>> I'm currently updating that part of the documentation - indeed it states
>> that two IPs are used, but in fact, you end up with only one VIP for the
>> API service.
>> I'll send the patch tonight
>>
>> *Razique Mahroua** - **Nuage & Co*
>> razique.mahr...@gmail.com
>> Tel : +33 9 72 37 94 15
>>
>> 
>>
>> Le 13 févr. 2013 à 20:05, Samuel Winchenbach  a
>> écrit :
>>
>> In that documentation it looks like each openstack service gets it own IP
>> (keystone is being assigned 192.168.42.103 and glance is getting
>> 192.168.42.104).
>>
>> I might be missing something too because in the section titled "Configure
>> the VIP" it create a primitive called "p_api-ip" (or p_ip_api if you read
>> the text above it) and then in "Adding Keystone resource to Pacemaker" it
>> creates a group with "p_ip_keystone"???
>>
>>
>> Stranger yet, "Configuring OpenStack Services to use High Available
>> Glance API" says:  "For Nova, for example, if your Glance API service IP
>> address is 192.168.42.104 as in the configuration explained here, you would
>> use the following line in your nova.conf file : glance_api_servers =
>> 192.168.42.103"  But, in the step before it set:  "registry_host =
>> 192.168.42.104"?
>>
>> So I am not sure which ip you would connect to here...
>>
>> Sam
>>
>>
>>
>> On Wed, Feb 13, 2013 at 1:29 PM, JuanFra Rodriguez Cardoso <
>> juanfra.rodriguez.card...@gmail.com> wrote:
>>
>>> Hi Samuel:
>>>
>>> Yes, it's possible with pacemaker. Look at
>>> http://docs.openstack.org/trunk/openstack-ha/content/ch-intro.html.
>>>
>>> Regards,
>>> JuanFra
>>>
>>>
>>> 2013/2/13 Samuel Winchenbach 
>>>
>>>>  Hi All,
>>>>
>>>> I currently have a HA OpenStack cluster running where the OpenStack
>>>> services are kept alive with a combination of haproxy and keepalived.
>>>>
>>>> Is it possible to configure pacemaker so that all the OpenStack
>>>> services  are served by the same IP?  With keepalived I have a virtual ip
>>>> that can move from server to server and haproxy sends the request to a
>>>> machine that has a "live" service.   This allows one (public) ip to handle
>>>> all incoming requests.  I believe it is the combination of VRRP/IPVS that
>>>> allows this.
>>>>
>>>>
>>>> Is it possible to do something similar with pacemaker?  I really don't
>>>> want to have an IP for each service, and I don't want to make it a
>>>> requirement that all OpenStack services must be running on the same server.
>>>>
>>>> Thanks... I hope this question is clear, I feel like I sort of
>>>> butchered the wording a bit.
>>>>
>>>> Sam
>>>>
>>>> ___
>>>> 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
>
>
___
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] can't run nova boot from command line (works from horizon)

[Sébastien Han]

nova network-list then look for the id and add the following to your
boot command:

nova boot bla bla bla --nic net-id= 

Let me know if it's better.

Cheers.

--
Regards,
Sébastien Han.


On Mon, Feb 4, 2013 at 6:24 PM, JR  wrote:
> Greetings,
>
> I'm running a devstack test cluster (all in one on a single host), which
> I've had up for days now.  Suddenly, I'm unable to run:
>
> nova boot --image d5784c25-9d3f-4023-8dd2-785d14fe251a --flavor 1
> --security-groups default  inst01
>
> which returns
> ERROR: The resource could not be found. (HTTP 404) (Request-ID:
> req-cb2d2545-395c-4582-ab9a-e594d0c4606e)
>
> I've looked at all the services which are started by devstack (and which
> are put into a screen session) and they are all running.
>
> nova image-list and other nova commands work. I'm also able to use glance.
>
> I see this output from nova-api:
> 2013-02-04 10:21:05.333 ERROR nova.api.openstack
> [req-4d9b4140-cdbb-4beb-9df9-38594f7fc070 demo demo] Caught error: No
> networks defined.
> Traceback (most recent call last):
>
>   File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 276, in
> _process_data
> rval = self.proxy.dispatch(ctxt, version, method, **args)
>
>   File "/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line
> 133, in dispatch
> return getattr(proxyobj, method)(ctxt, **kwargs)
>
>   File "/opt/stack/nova/nova/network/manager.py", line 1845, in
> validate_networks
> self._get_networks_by_uuids(context, network_uuids)
>
>   File "/opt/stack/nova/nova/network/manager.py", line 1872, in
> _get_networks_by_uuids
> project_only="allow_none")
>
>   File "/opt/stack/nova/nova/db/api.py", line 865, in
> network_get_all_by_uuids
> project_only=project_only)
>
>   File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 134, in wrapper
> return f(*args, **kwargs)
>
>   File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 2206, in
> network_get_all_by_uuids
> raise exception.NoNetworksFound()
>
>
> Nothing has changed in the configuration of the environment.  Any ideas?
>
> Thanks
> JR
>
>
> ___
> 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] can't run nova boot from command line (works from horizon)

[Sébastien Han]

hum ok now I wonder if you created a network or not?

# nova-manage network list

?
--
Regards,
Sébastien Han.


On Mon, Feb 4, 2013 at 7:09 PM, JR  wrote:
> Hi Sébastien
>
> Problem is, I can't run nova network-list either!
>
> stack@gpfs6-int:~$ nova network-list
> ERROR: Not found (HTTP 404)
>
> I can, however, run:
> stack@gpfs6-int:~$ nova net-list
> +--+-+---+
> | ID   | Label   | CIDR  |
> +--+-+---+
> | 1c6ede3d-8c7d-46e5-8df8-135f74088088 | private | 172.30.1.0/24 |
> +--+-+---+
>
> The error I see (with nova network-list) is:
>
> 2013-02-04 10:57:36.666 3209 INFO nova.osapi_compute.wsgi.server [-]
> (3209) accepted ('10.200.20.153', 33874)
> 2013-02-04 10:57:36.723 INFO nova.osapi_compute.wsgi.server
> [req-38b415b4-46ca-4e63-8bf6-3b111835716b admin admin] 10.200.20.153
> "GET /v2/fa2e432641da4605bd01e3d2b043b88b/os-networksv2 HTTP/1.1"
> status: 404 len: 176 time: 0.0550740
>
> If I run your command (i.e., with --nic ..), it still fails with this
> output from nova-api:
>
> 2013-02-04 11:04:26.314 4477 TRACE nova.api.openstack   File
> "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 2219, in
> network_get_all_by_uuids
> 2013-02-04 11:04:26.314 4477 TRACE nova.api.openstack
> network_uuid=network_uuid, project_id=context.project_id)
> 2013-02-04 11:04:26.314 4477 TRACE nova.api.openstack
> NetworkNotFoundForProject: Either Network uuid
> ---- is not present or is not assigned
> to the project fa2e432641da4605bd01e3d2b043b88b.
> 2013-02-04 11:04:26.322 INFO nova.api.openstack
> [req-367e5855-ed39-425d-9138-33c19cfa4826 admin admin]
> http://10.200.20.153:8774/v2/fa2e432641da4605bd01e3d2b043b88b/servers
> returned with HTTP 404
> 2013-02-04 11:04:26.324 INFO nova.osapi_compute.wsgi.server
> [req-367e5855-ed39-425d-9138-33c19cfa4826 admin admin] 10.200.20.153
> "POST /v2/fa2e432641da4605bd01e3d2b043b88b/servers HTTP/1.1" status: 404
> len: 272 time: 0.3524289
>
> Which, I think, is a bit different from the first error.
>
> Thanks
> John
>
> On 2/4/2013 12:53 PM, Sébastien Han wrote:
>> nova network-list then look for the id and add the following to your
>> boot command:
>>
>> nova boot bla bla bla --nic net-id= 
>>
>> Let me know if it's better.
>>
>> Cheers.
>>
>> --
>> Regards,
>> Sébastien Han.
>>
>>
>> On Mon, Feb 4, 2013 at 6:24 PM, JR  wrote:
>>> Greetings,
>>>
>>> I'm running a devstack test cluster (all in one on a single host), which
>>> I've had up for days now.  Suddenly, I'm unable to run:
>>>
>>> nova boot --image d5784c25-9d3f-4023-8dd2-785d14fe251a --flavor 1
>>> --security-groups default  inst01
>>>
>>> which returns
>>> ERROR: The resource could not be found. (HTTP 404) (Request-ID:
>>> req-cb2d2545-395c-4582-ab9a-e594d0c4606e)
>>>
>>> I've looked at all the services which are started by devstack (and which
>>> are put into a screen session) and they are all running.
>>>
>>> nova image-list and other nova commands work. I'm also able to use glance.
>>>
>>> I see this output from nova-api:
>>> 2013-02-04 10:21:05.333 ERROR nova.api.openstack
>>> [req-4d9b4140-cdbb-4beb-9df9-38594f7fc070 demo demo] Caught error: No
>>> networks defined.
>>> Traceback (most recent call last):
>>>
>>>   File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 276, in
>>> _process_data
>>> rval = self.proxy.dispatch(ctxt, version, method, **args)
>>>
>>>   File "/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line
>>> 133, in dispatch
>>> return getattr(proxyobj, method)(ctxt, **kwargs)
>>>
>>>   File "/opt/stack/nova/nova/network/manager.py", line 1845, in
>>> validate_networks
>>> self._get_networks_by_uuids(context, network_uuids)
>>>
>>>   File "/opt/stack/nova/nova/network/manager.py", line 1872, in
>>> _get_networks_by_uuids
>>> project_only="allow_none")
>>>
>>>   File "/opt/stack/nova/nova/db/api.py", line 865, in
>>> network_get_all_by_uuids
>>> project_only=project_only)
>>>
>>>   File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 134, in wra

Re: [Openstack] nova ceph integration

[Sébastien Han]

+1 John

Since CephFS is not production ready what you can do is map RBD device
to all of your compute nodes and then mount them in
/var/lib/nova/instances. The downside of this that you have way more
IOPS since you only have one RBD per compute node for EVERY VMs that
will end up into this compute. With the boot from volume it's one RBD
per instance which brings way more IOPS to your instance. Still with
boot from volume you can also enjoy the rbd cache on the client side,
cache that will also helps with buffered IO.

Cheers!
--
Regards,
Sébastien Han.


On Thu, Jan 31, 2013 at 7:53 PM, John Griffith
 wrote:
>
>
> On Thu, Jan 31, 2013 at 11:43 AM, Sébastien Han 
> wrote:
>>
>> Try to have a look at the boot from volume feature. Basically the disk
>> base of your instance is an RBD volume from Ceph. Something will be
>> remain in /var/lib/nova/instances but it's only the kvm xml file.
>>
>> http://ceph.com/docs/master/rbd/rbd-openstack/?highlight=openstack
>>
>> Cheers!
>> --
>> Regards,
>> Sébastien Han.
>>
>>
>> On Thu, Jan 31, 2013 at 7:40 AM, Wolfgang Hennerbichler
>>  wrote:
>> > Hi,
>> >
>> > I'm sorry if this has been asked before. My question is: can I integrate
>> > ceph into openstack's nova & cinder in a way, that I don't need
>> > /var/lib/nova/instances anymore? I'd like to have EVERYTHING in ceph,
>> > starting from glance images to nova-disk-images and volumes (cinder). And
>> > more important: Can this be done in a way so that my horizon-users can 
>> > still
>> > use horizon (including snapshotting) without the need of abusing the
>> > command-line? :)
>> > I've read that cinder and glance are supported, but I didn't find much
>> > information on nova-disk-images and ceph.
>> >
>> > thanks for a reply
>> > wolfgang
>> > ___
>> > 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
>
>
> Boot from volume is one good option, another is to setup ceph and point
> nova's insances_path to point to it.  I haven't done it with Ceph but I've
> done this sort of thing using iSCSI mounts on the compute node.

___
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] nova ceph integration

[Sébastien Han]

Try to have a look at the boot from volume feature. Basically the disk
base of your instance is an RBD volume from Ceph. Something will be
remain in /var/lib/nova/instances but it's only the kvm xml file.

http://ceph.com/docs/master/rbd/rbd-openstack/?highlight=openstack

Cheers!
--
Regards,
Sébastien Han.


On Thu, Jan 31, 2013 at 7:40 AM, Wolfgang Hennerbichler
 wrote:
> Hi,
>
> I'm sorry if this has been asked before. My question is: can I integrate ceph 
> into openstack's nova & cinder in a way, that I don't need 
> /var/lib/nova/instances anymore? I'd like to have EVERYTHING in ceph, 
> starting from glance images to nova-disk-images and volumes (cinder). And 
> more important: Can this be done in a way so that my horizon-users can still 
> use horizon (including snapshotting) without the need of abusing the 
> command-line? :)
> I've read that cinder and glance are supported, but I didn't find much 
> information on nova-disk-images and ceph.
>
> thanks for a reply
> wolfgang
> ___
> 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] List of Cinder compatible devices

[Sébastien Han]

Just added some stuff about RBD where E refers to Essex.

--
Regards,
Sébastien Han.


On Thu, Jan 31, 2013 at 11:20 AM, Avishay Traeger  wrote:
> openstack-bounces+avishay=il.ibm@lists.launchpad.net wrote on
> 01/31/2013 12:37:07 AM:
>> From: Tom Fifield 
>> To: openstack@lists.launchpad.net,
>> Date: 01/31/2013 12:38 AM
>> Subject: Re: [Openstack] List of Cinder compatible devices
>> Sent by: openstack-bounces+avishay=il.ibm@lists.launchpad.net
>>
>> Here's a starting point:
>>
>> http://wiki.openstack.org/CinderSupportMatrix
>>
>> Regards,
>>
>> Tom
>
> Tom,
> Thanks for doing this.  I recommend that instead of "Y", we should put the
> letter of the version in which the feature first appeared.  So for example,
> "E", "F", "G", ...
>
> Thanks,
> Avishay
>
>
> ___
> 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] List of Cinder compatible devices

[Sébastien Han]

+ RBD (Ceph)

+1 for the matrix, this will be really nice :-)
--
Regards,
Sébastien Han.


On Wed, Jan 30, 2013 at 5:04 PM, Tim Bell  wrote:
>
>
> Is there a list of devices which are currently compatible with cinder and
> their relative functionality ?
>
>
>
> Looking through the source code, there are EMC, IBM, NetApp, Nexenta but it
> is not clear which models are supported or if there are other products also.
>
>
>
> A functionality matrix (like there is for hypervisors in Nova) would be very
> useful.
>
>
>
> Tim
>
>
>
>
> ___
> 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] Bypassing the keypair in Folsom

[Sébastien Han]

so you prefer to be asked for a password instead of log in passwordless?

as suggested, edit the base image and create a password for the user :)

--
Regards,
Sébastien Han.


On Tue, Jan 22, 2013 at 6:08 PM, Balamurugan V G
 wrote:
> My ssh debug logs are below:
>
> $ ssh -vvv root@1.1.1.1
> OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: Applying options for *
> debug2: ssh_connect: needpriv 0
> debug1: Connecting to 1.1.1.1 [1.1.1.1] port 22.
> debug1: Connection established.
> debug3: Incorrect RSA1 identifier
> debug3: Could not load "/home/balu/.ssh/id_rsa" as a RSA1 public key
> debug1: identity file /home/balu/.ssh/id_rsa type 1
> debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
> debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
> debug1: identity file /home/balu/.ssh/id_rsa-cert type -1
> debug1: identity file /home/balu/.ssh/id_dsa type -1
> debug1: identity file /home/balu/.ssh/id_dsa-cert type -1
> debug1: identity file /home/balu/.ssh/id_ecdsa type -1
> debug1: identity file /home/balu/.ssh/id_ecdsa-cert type -1
> debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1
> Debian-5ubuntu1
> debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1 pat OpenSSH*
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
> debug2: fd 3 setting O_NONBLOCK
> debug3: load_hostkeys: loading entries for host "1.1.1.1" from file
> "/home/balu/.ssh/known_hosts"
> debug3: load_hostkeys: loaded 0 keys
> debug1: SSH2_MSG_KEXINIT sent
> Connection closed by 1.1.1.1
>
> Regards,
> Balu
>
>
> On Tue, Jan 22, 2013 at 10:31 PM, Balamurugan V G 
> wrote:
>>
>> Yes but I want to skip this feature of keypairs. I want to be able to SSH
>> with out needing the keypairs since security is not a concern in my private
>> cloud.
>>
>> Thanks,
>> Balu
>>
>> On Tue, Jan 22, 2013 at 10:29 PM, JuanFra Rodriguez Cardoso
>>  wrote:
>>>
>>> Hi Balu:
>>>
>>> Before launching an instance, you have to create a keypair
>>> (YOUR_DASHBOARD_IP/dashboard/nova/access_and_security/).
>>> Then, next time you launch an instance, you can choose that keypair
>>> created previously.
>>>
>>> Regards,
>>> JuanFra.
>>>
>>> 2013/1/22 Balamurugan V G 
>>>>
>>>> Hi,
>>>>
>>>> I have a Folsom private openstack cloud in which security is not a
>>>> concern. That is I dont really need the security groups and keypairs etc
>>>> offered by openstack. So all my instances are launched as part of the
>>>> default security group. I have even allowed all TCP and UDP ports(1 to
>>>> 65535) and ICMP.
>>>>
>>>> But when I try to SSH to the floating IP assigned to a Ubuntu instance,
>>>> I get connection refused. When I so 'ssh -vvv', I can see that the
>>>> connection is getting establish but is getting terminated. It seems due to
>>>> missing key pair.
>>>>
>>>> Is there a way to bypass the keypairs.
>>>>
>>>> Regards,
>>>> Balu
>>>>
>>>> ___
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>
>>>
>>>
>>> --
>>> JuanFra
>>
>>
>
>
> ___
> 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] Migrate Instance to another Tenant ID in the same environment

[Sébastien Han]

If an admin user put it public, this is also possible.
--
Regards,
Sébastien Han.


On Fri, Jan 11, 2013 at 3:40 AM, Lei Zhang  wrote:
> why not try boot from snapshot. That's will save some time.
>
>
> On Thu, Jan 10, 2013 at 5:18 AM, Sébastien Han 
> wrote:
>>
>> Moving instances from project to project is not possible however what
>> you can do is (safe way):
>>
>> - as an admin user
>> - snapshot the image from env 1
>> - grab the snapshotted file from your glance store
>> - import the snapshot into glance
>> - make the image public
>> - run the snapshot from env 2
>> - enjoy!
>>
>> Cheers!
>>
>> --
>> Regards,
>> Sébastien Han.
>>
>>
>> On Wed, Jan 9, 2013 at 8:14 PM, Alex Vitola  wrote:
>> > I have 2 projects in my environment:
>> >
>> > ProjectQA1: ID -> 0001
>> > ProjectQA2: ID -> 0002
>> >
>> > root@Controller:# keystone tenant-list
>> > +-++-+
>> > | id  |name| enabled |
>> > +-++-+
>> > | 0001| ProjectQA1 |   True  |
>> > | 0002| ProjectQA2 |   True  |
>> > +--++-+
>> >
>> > In Project 1 there are 1 instance
>> > In Project 2 there are 7 instances
>> >
>> > root@Controller:# nova usage-list
>> >
>> > +---+---+--+---+---+
>> > | Tenant ID | Instances | RAM MB-Hours | CPU Hours | Disk GB-Hours |
>> > +---+---+--+---+---+
>> > | 0001  | 1 | 12533.78 | 24.48 | 244.80|
>> > | 0002  | 7 | 127447.40| 171.17| 2100.45   |
>> > +---+---+--+---+---+
>> >
>> > Is it possible to move this instance of Project 1 for 2?
>> >
>> > root@Controller:# nova list
>> > +--+---+++
>> > | ID   | Name  | Status | Networks   |
>> > +--+---+++
>> > | 9991 | QA-07 | ACTICE | Net-Demo=200.100.50.25 |
>> > +--+---+++
>> >
>> > Move ID 9991/QA-07
>> >
>> > from: Tenant ID 0001
>> > to: Tenant ID 0002
>> >
>> > Is that possible?
>> >
>> >
>> >
>> > Att
>> >
>> > Alex Vitola
>> > System Administrator
>> >
>> > ___
>> > 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] Migrate Instance to another Tenant ID in the same environment

[Sébastien Han]

Cool!


--
Regards,
Sébastien Han.


On Thu, Jan 10, 2013 at 11:15 AM, Alex Vitola  wrote:
> Changed directly by the database.
>
> Not the best way but I did because it was an environment.
>
> So far I have not found any problems
>
>
> mysql> use nova;
> mysql> UPDATE `nova`.`instances` SET `user_id` =
> 'c892202c2a134b8e9f19c047f29c60ee', `project_id` =
> 'debd50b4ec2b4905a3296ac0f0971849' WHERE `instances`.`id` =7;
>
>
> att
>
> Alex Vitola
>
>
> 2013/1/10 Razique Mahroua 
>>
>> +1
>>
>> Seb, have you ever tried to change the tenant id for an instance into the 
>> database and reboot/ recover it? I wonder how nova behaves into such case
>>
>> Razique Mahroua - Nuage & Co
>> razique.mahr...@gmail.com
>> Tel : +33 9 72 37 94 15
>>
>>
>> Le 9 janv. 2013 à 22:18, Sébastien Han  a écrit :
>>
>> Moving instances from project to project is not possible however what
>> you can do is (safe way):
>>
>> - as an admin user
>> - snapshot the image from env 1
>> - grab the snapshotted file from your glance store
>> - import the snapshot into glance
>> - make the image public
>> - run the snapshot from env 2
>> - enjoy!
>>
>> Cheers!
>>
>> --
>> Regards,
>> Sébastien Han.
>>
>>
>> On Wed, Jan 9, 2013 at 8:14 PM, Alex Vitola  wrote:
>>
>> I have 2 projects in my environment:
>>
>> ProjectQA1: ID -> 0001
>> ProjectQA2: ID -> 0002
>>
>> root@Controller:# keystone tenant-list
>> +-++-+
>> | id  |name| enabled |
>> +-++-+
>> | 0001| ProjectQA1 |   True  |
>> | 0002| ProjectQA2 |   True  |
>> +--++-+
>>
>> In Project 1 there are 1 instance
>> In Project 2 there are 7 instances
>>
>> root@Controller:# nova usage-list
>>
>> +---+---+--+---+---+
>> | Tenant ID | Instances | RAM MB-Hours | CPU Hours | Disk GB-Hours |
>> +---+---+--+---+---+
>> | 0001  | 1 | 12533.78 | 24.48 | 244.80|
>> | 0002  | 7 | 127447.40| 171.17| 2100.45   |
>> +---+---+--+---+---+
>>
>> Is it possible to move this instance of Project 1 for 2?
>>
>> root@Controller:# nova list
>> +--+---+++
>> | ID   | Name  | Status | Networks   |
>> +--+---+++
>> | 9991 | QA-07 | ACTICE | Net-Demo=200.100.50.25 |
>> +--+---+++
>>
>> Move ID 9991/QA-07
>>
>> from: Tenant ID 0001
>> to: Tenant ID 0002
>>
>> Is that possible?
>>
>>
>>
>> Att
>>
>> Alex Vitola
>> System Administrator
>>
>> ___
>> 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

___
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] Migrate Instance to another Tenant ID in the same environment

[Sébastien Han]

Moving instances from project to project is not possible however what
you can do is (safe way):

- as an admin user
- snapshot the image from env 1
- grab the snapshotted file from your glance store
- import the snapshot into glance
- make the image public
- run the snapshot from env 2
- enjoy!

Cheers!

--
Regards,
Sébastien Han.


On Wed, Jan 9, 2013 at 8:14 PM, Alex Vitola  wrote:
> I have 2 projects in my environment:
>
> ProjectQA1: ID -> 0001
> ProjectQA2: ID -> 0002
>
> root@Controller:# keystone tenant-list
> +-++-+
> | id  |name| enabled |
> +-++-+
> | 0001| ProjectQA1 |   True  |
> | 0002| ProjectQA2 |   True  |
> +--++-+
>
> In Project 1 there are 1 instance
> In Project 2 there are 7 instances
>
> root@Controller:# nova usage-list
>
> +---+---+--+---+---+
> | Tenant ID | Instances | RAM MB-Hours | CPU Hours | Disk GB-Hours |
> +---+---+--+---+---+
> | 0001  | 1 | 12533.78 | 24.48 | 244.80|
> | 0002  | 7 | 127447.40| 171.17| 2100.45   |
> +---+---+--+---+---+
>
> Is it possible to move this instance of Project 1 for 2?
>
> root@Controller:# nova list
> +--+---+++
> | ID   | Name  | Status | Networks   |
> +--+---+++
> | 9991 | QA-07 | ACTICE | Net-Demo=200.100.50.25 |
> +--+---+++
>
> Move ID 9991/QA-07
>
> from: Tenant ID 0001
> to: Tenant ID 0002
>
> Is that possible?
>
>
>
> Att
>
> Alex Vitola
> System Administrator
>
> ___
> 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] Nova (compute) and syslog

[Sébastien Han]

Hi,

Stupid question, did you restart compute and api service?

I don't have any problems with those flags.

--
Regards,
Sébastien Han.


On Mon, Jan 7, 2013 at 9:58 AM, Robert van Leeuwen <
robert.vanleeu...@spilgames.com> wrote:

> Hi,
>
> I'm trying to get all logging into syslog.
> I have modified the nova.conf:
> use_syslog= True
> syslog_log_facility= LOG_LOCAL0
>
> However it appears for most components logging is still going to
> /var/log/nova/
> So the api.log and compute.log are still going there.
> There are some messages going to syslog but the amount seems to be trivial
> compared to stuff going to /var/log
>
> Do I have  a wrong understanding of the use_syslog directive? Does it only
> apply to a subset of the logging?
> Or is something broken?
>
> Anyone who has set this up who can help me out?
>
> Running Folsom on SL6..
>
> Thanks,
> Robert
> ___
> 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] Openstack High Availability

[Sébastien Han]

Thanks Razique,

I still need to edit the official HA doc to give details about this
setup, I don't really have the time this week.
I hope I can save some time before the end of the year.

Cheers!
--
Regards,
Sébastien Han.


On Tue, Dec 18, 2012 at 12:13 AM, Razique Mahroua
 wrote:
> Great links
> thanks for these Seb :)
>
> Le 17 déc. 2012 à 22:48, Sébastien Han  a écrit :
>
> Hi,
>
> For the others OpenStack components please follow:
>
> http://www.sebastien-han.fr/blog/2012/06/28/openstack-glance-keystone-ha/
> http://www.hastexo.com/blogs/martin/2012/04/03/bringing-high-availability-openstack-keystone-and-glance
> http://www.sebastien-han.fr/blog/2012/07/02/openstack-nova-components-ha/
>
> For the latest article please use this repo, this our new location with
> several branches (Essex/Folsom).
>
> https://github.com/madkiss/openstack-resource-agents
>
> --
> Regards,
> Sébastien Han.
>
>
>
> On Mon, Dec 17, 2012 at 9:56 PM, Eugene Kirpichov 
> wrote:
>>
>> Right, you only need HA for swift-proxy where a simple load balancer
>> suffices.
>>
>> On Dec 17, 2012, at 12:42 PM, Caitlin Bestler
>>  wrote:
>>
>> >
>> >
>> > Eugene Kirpichov wrote:
>> >
>> >> I suggest you to read a series of our blogposts on H/A in openstack (in
>> >> this order):
>> >> http://www.mirantis.com/blog/intro-to-openstack-in-production/
>> >> http://www.mirantis.com/blog/ha-platform-components-mysql-rabbitmq/
>> >>
>> >> http://www.mirantis.com/blog/software-high-availability-load-balancing-openstack-cloud-api-servic/
>> >> http://www.mirantis.com/blog/117072/
>> >
>> >> Sorry for the shameless promotion but I actually think it's relevant :)
>> >
>> > Good articles. The one thing they don't cover is Swift, which mostly
>> > does not need to be covered
>> > since the Swift service is designed to be highly available even if the
>> > individual servers are not.
>> >
>>
>> ___
>> 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] Openstack High Availability

[Sébastien Han]

Hi,

For the others OpenStack components please follow:

http://www.sebastien-han.fr/blog/2012/06/28/openstack-glance-keystone-ha/
http://www.hastexo.com/blogs/martin/2012/04/03/bringing-high-availability-openstack-keystone-and-glance
http://www.sebastien-han.fr/blog/2012/07/02/openstack-nova-components-ha/

For the latest article *please use* this repo, this our new location with
several branches (Essex/Folsom).

https://github.com/madkiss/openstack-resource-agents

--
Regards,
Sébastien Han.



On Mon, Dec 17, 2012 at 9:56 PM, Eugene Kirpichov wrote:

> Right, you only need HA for swift-proxy where a simple load balancer
> suffices.
>
> On Dec 17, 2012, at 12:42 PM, Caitlin Bestler 
> wrote:
>
> >
> >
> > Eugene Kirpichov wrote:
> >
> >> I suggest you to read a series of our blogposts on H/A in openstack (in
> this order):
> >> http://www.mirantis.com/blog/intro-to-openstack-in-production/
> >> http://www.mirantis.com/blog/ha-platform-components-mysql-rabbitmq/
> >>
> http://www.mirantis.com/blog/software-high-availability-load-balancing-openstack-cloud-api-servic/
> >> http://www.mirantis.com/blog/117072/
> >
> >> Sorry for the shameless promotion but I actually think it's relevant :)
> >
> > Good articles. The one thing they don't cover is Swift, which mostly
> does not need to be covered
> > since the Swift service is designed to be highly available even if the
> individual servers are not.
> >
>
> ___
> 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] [ERROR] refresh_instance_security_rules

[Sébastien Han]

Hi Vish,

The logs don't show more, even after enabling DEBUG logs...
See debug mode below right away before and after the message:

http://pastebin.com/1LCXuaVi

I forgot to mention but it _only_ appears while rolling out a new instance.

Thanks.


--
Regards,
Sébastien Han.



On Sat, Dec 15, 2012 at 12:32 AM, Vishvananda Ishaya
wrote:

> Was there more to the error? The underlying exception isn't listed.
>
> Vish
>
> On Dec 14, 2012, at 7:24 AM, Sébastien Han 
> wrote:
>
> Hi Stackers,
>
> I run Folsom on Ubuntu 12.04.
>
> Every time I run a new instance I get this ERROR in the compute logs.
>
> Dec 12 23:46:29 c2-compute-02 2012-12-12 23:46:29 ERROR
> nova.openstack.common.rpc.amqp [-] Exception during message handling#
> 0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp Traceback
> (most recent call last):#0122012-12-12 23:46:29 TRACE
> nova.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py",
> line 275, in _process_data#0122012-12-12 23:46:29 TRACE
> nova.openstack.common.rpc.amqp rval = self.proxy.dispatch(ctxt,
> version, method, **args)#0122012-12-12 23:46:29 TRACE
> nova.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/dispatcher.py",
> line 145, in dispatch#0122012-12-12 23:46:29 TRACE
> nova.openstack.common.rpc.amqp return getattr(proxyobj, method)(ctxt,
> **kwargs)#0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp
> File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 117, 
> inwrapped#
> 0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp
> temp_level, payload)#0122012-12-12 23:46:29 TRACE
> nova.openstack.common.rpc.amqp   File "/usr/lib/python2.7/contextlib.py",
> line 24, in __exit__#0122012-12-12 23:46:29 TRACE
> nova.openstack.common.rpc.amqp self.gen.next()#0122012-12-12 
> 23:46:29TRACE nova.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/nova/exception.py", line 92, in wrapped#
> 0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp 
> returnf(*args, **kw)#
> 0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 380, 
> inrefresh_instance_security_rules#
> 0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp 
> returnself.driver.refresh_instance_security_rules(instance)#
> 0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2189,
> in refresh_instance_security_rules#0122012-12-12 23:46:29 TRACE
> nova.openstack.common.rpc.amqp
> self.firewall_driver.refresh_instance_security_rules(instance)#
>
>
> This error seems harmless, as far as I can tell everything works
> perfectly. Even so I'd like to have some input about it (ideally a fix
> because it pollutes my logs).
>
> Thank you in advance.
> --
> Regards,
> Sébastien Han.
>
>  ___
> 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] [ERROR] refresh_instance_security_rules

[Sébastien Han]

Hi Stackers,

I run Folsom on Ubuntu 12.04.

Every time I run a new instance I get this ERROR in the compute logs.

Dec 12 23:46:29 c2-compute-02 2012-12-12 23:46:29 ERROR
nova.openstack.common.rpc.amqp [-] Exception during message handling#0122012
-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp Traceback (most recent
call last):#0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp
File "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py",
line 275, in _process_data#0122012-12-12 23:46:29 TRACE
nova.openstack.common.rpc.amqp rval = self.proxy.dispatch(ctxt,
version, method, **args)#0122012-12-12 23:46:29 TRACE
nova.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/dispatcher.py",
line 145, in dispatch#0122012-12-12 23:46:29 TRACE
nova.openstack.common.rpc.amqp return getattr(proxyobj, method)(ctxt,
**kwargs)#0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp
File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 117, inwrapped#
0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp temp_level,
payload)#0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/contextlib.py", line 24, in __exit__#0122012-12-12 23:46
:29 TRACE nova.openstack.common.rpc.amqp self.gen.next()#0122012-12-12
23:46:29 TRACE nova.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/nova/exception.py", line 92, in wrapped#
0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp
returnf(*args, **kw)#
0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 380,
inrefresh_instance_security_rules#
0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp
returnself.driver.refresh_instance_security_rules(instance)#
0122012-12-12 23:46:29 TRACE nova.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2189,
in refresh_instance_security_rules#0122012-12-12 23:46:29 TRACE
nova.openstack.common.rpc.amqp
self.firewall_driver.refresh_instance_security_rules(instance)#


This error seems harmless, as far as I can tell everything works perfectly.
Even so I'd like to have some input about it (ideally a fix because it
pollutes my logs).

Thank you in advance.
--
Regards,
Sébastien Han.
___
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] Is there any way to migrate the Instance between the projects/tenants?

[Sébastien Han]

>
> The step 2 and 3 can be left out. Because the instance snapshot can be
> marked public. Then we can lanuch instance from the snapshot in another
> tenant.


Forgot that one ;-)

 How about when the instance is attached with volume? How to migrate the
> Volume? It seems that the Volume can not be marked publice? Do you have any
> ideas?


There is a dirty hack that you could perform for that. What you could do is
(depends on your storage backend):

- detach the volume from project A
- create a dummy volume on project B
- make pointed the volume from project A to the dummy in project B
- delete the volume from project A

If you use Ceph RBD it's really easy for example.

For the rest I don't know.

--
Bien cordialement.
Sébastien HAN.



On Thu, Nov 29, 2012 at 9:55 AM, Lei Zhang  wrote:

> Hi Sébastien,
>
> Good ideas. There is a very tricky way to solve this problem.
>
> In addition,
> The step 2 and 3 can be left out. Because the instance snapshot can be
> marked public. Then we can lanuch instance from the snapshot in another
> tenant.
> Anothe Question,
> How about when the instance is attached with volume? How to migrate the
> Volume? It seems that the Volume can not be marked publice? Do you have any
> ideas?
>
>
> On Thu, Nov 29, 2012 at 3:38 PM, Sébastien Han wrote:
>
>> Hi,
>>
>> What I will do to achieve what you want:
>>
>> _ take a snapshot of your instance
>> _ export the snapshot from wherever it's stored (filesystem for instance)
>> _ import it to Glance, make the image to public or assign it to the
>> tenant (not 100% sure if the latest is possible though...)
>> _ run a new vm with the based image previously created
>>
>> Some steps could be avoided like step 2 and 3. You could use the admin
>> user to snapshot and then run the snapshot from the other tenan. However
>> it's NOT recommended.
>>
>> Cheers.
>>
>> On Nov 29, 2012 7:47 AM, "Tim Bell"  wrote:
>> >
>> >
>> >
>> > We were also interested in this function but could not find an easy way
>> to do it.
>> >
>> >
>> >
>> > The operation becomes more complex when there are attached volumes and
>> potentially different permissions between the two projects.
>> >
>> >
>> >
>> > Tim
>> >
>> >
>> >
>> > From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:
>> openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Lei
>> Zhang
>> > Sent: 29 November 2012 06:09
>> > To: openstack@lists.launchpad.net
>> > Subject: [Openstack] Is there any way to migrate the Instance between
>> the projects/tenants?
>> >
>> >
>> >
>> > Hi all,
>> >
>> >
>> >
>> > As the subject say, is there any way to do this? I search the Internet
>> and only found the migration bewteen two physical machine.
>> >
>> >
>> > thanks
>> >
>> > --
>> >
>> > 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
>> >
>>
>>
>
>
> --
> 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] Is there any way to migrate the Instance between the projects/tenants?

[Sébastien Han]

Hi,

What I will do to achieve what you want:

_ take a snapshot of your instance
_ export the snapshot from wherever it's stored (filesystem for instance)
_ import it to Glance, make the image to public or assign it to the tenant
(not 100% sure if the latest is possible though...)
_ run a new vm with the based image previously created

Some steps could be avoided like step 2 and 3. You could use the admin user
to snapshot and then run the snapshot from the other tenan. However it's
NOT recommended.

Cheers.

On Nov 29, 2012 7:47 AM, "Tim Bell"  wrote:
>
>
>
> We were also interested in this function but could not find an easy way
to do it.
>
>
>
> The operation becomes more complex when there are attached volumes and
potentially different permissions between the two projects.
>
>
>
> Tim
>
>
>
> From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:
openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Lei
Zhang
> Sent: 29 November 2012 06:09
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Is there any way to migrate the Instance between the
projects/tenants?
>
>
>
> Hi all,
>
>
>
> As the subject say, is there any way to do this? I search the Internet
and only found the migration bewteen two physical machine.
>
>
> thanks
>
> --
>
> 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

Re: [Openstack] how to let the instance name (instance-xxx) equal to the hostname of the instance (chosen by the user)??

[Sébastien Han]

Hi Vish,

Also the name is not unique, so if you do this you will have big problems
> if two users chose the same name.


I manage and decide instance names, so this should not be a problem.

Thanks ;)


On Wed, Nov 28, 2012 at 11:19 PM, Vishvananda Ishaya
wrote:

>
> On Nov 28, 2012, at 2:16 PM, Vishvananda Ishaya 
> wrote:
>
> >
> > On Nov 28, 2012, at 2:08 PM, Sébastien Han 
> wrote:
> >
> >> Hi,
> >>
> >> Just tried this, it works but I'd also like to rename
> /var/lib/nova/instances/ according to the hostname. At the moment this only
> rename (output from nova show):
> >>
> >> | OS-EXT-SRV-ATTR:instance_name   | mon-nom
> >>
> >> Is it possible?
> >>
> >> Cheers!
> >
> > Changing the name should change the dir in /var/lib/nova/instances,
> although it must be in nova.conf on the compute host and nova-compute will
> need to be restarted before you launch the instance.
> >
> > Vish
> >
>
> Also the name is not unique, so if you do this you will have big problems
> if two users chose the same name.
>
> Vish
___
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] how to let the instance name (instance-xxx) equal to the hostname of the instance (chosen by the user)??

[Sébastien Han]

Hi,

Just tried this, it works but I'd also like to rename
/var/lib/nova/instances/ according to the hostname. At the moment this only
rename (output from nova show):

| OS-EXT-SRV-ATTR:instance_name   | mon-nom

Is it possible?

Cheers!

On Wed, Nov 28, 2012 at 7:31 PM, John Garbutt wrote:

> I think this is the flag you want to change and its default:
>
> instance_name_template="instance-%08x"
>
> ** **
>
> You should try:
>
> instance_name_template="%(hostname)s"
>
> ** **
>
> This is the code that deals with it:
>
>
> https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L203
> 
>
> ** **
>
> This is where the name gets set inside XenAPI:
>
>
> https://github.com/openstack/nova/blob/master/nova/virt/xenapi/vmops.py#L260
> 
>
> Which eventually gets here (i.e. you could just hack this file, if the
> above fails):
>
>
> https://github.com/openstack/nova/blob/master/nova/virt/xenapi/vm_utils.py#L193
> 
>
> ** **
>
> Hope that helps,
>
> John
>
> ** **
>
> *From:* Afef MDHAFFAR [mailto:afef.mdhaf...@gmail.com]
> *Sent:* 28 November 2012 18:18
> *To:* John Garbutt
> *Cc:* openstack@lists.launchpad.net
> *Subject:* Re: [Openstack] how to let the instance name (instance-xxx)
> equal to the hostname of the instance (chosen by the user)??
>
> ** **
>
> Hi,
>
> ** **
>
> Yes - when you list your vms via xe vm-list, you get the name-label of the
> instance. 
>
> The question is how to modify openstack to let the hostname of the created
> instance equal to this name-label?
>
> ** **
>
> Thank you,
>
> Afef
>
> ** **
>
> 2012/11/28 John Garbutt 
>
> Hi,
>
>  
>
> Not quick sure which “name” of the instance you are refereeing to.
>
>  
>
> Do you mean when you open XenCenter it shows you a different name?
>
>  
>
> Thanks,
>
> John
>
>  
>
> *From:* openstack-bounces+john.garbutt=citrix@lists.launchpad.net[mailto:
> openstack-bounces+john.garbutt=citrix@lists.launchpad.net] *On Behalf
> Of *Afef MDHAFFAR
> *Sent:* 23 November 2012 17:22
> *To:* openstack@lists.launchpad.net
> *Subject:* [Openstack] how to let the instance name (instance-xxx) equal
> to the hostname of the instance (chosen by the user)??
>
>  
>
> Hi all,
>
>  
>
> Due to some requirements, I have to modify openstack source code in order
> to let the name of the instance (in Xen Server) equal to the hostname of
> the instance (chosen by the user).
>
> Is it possible to do that by only configuring openstack? If yes, could you
> please guide me to the suitable flag?
>
> If not, could you please guide me to the right python files that need to
> be changed.
>
> I use the folsom release, with XCP as a virtualization technology. 
>
>  
>
> Thank you,
>
> Afef
>
>
>
> 
>
> ** **
>
> --
> Afef MDHAFFAR
> http://www.redcad.org/members/mdhaffar/
>
>
> 
>
> ___
> 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] Ceph + Nova

[Sébastien Han]

As far I'm concerned, I will never put config files on share storage
(especially on a non-production ready), these are too critical. I will only
do it if the application specifically requires it like shared web
applications that needs auto vhost sync (or stuff like that).

If you want to keep them update & sync, simply manage this with git &
puppet ;)

My 2 cents...

On Wed, Nov 21, 2012 at 10:40 PM, Razique Mahroua  wrote:

> That's i think a clever approach - to set a data cluster as a backend for
> the configuration files - which are de facto as important as the instances
> themselves.
> Regarding the performance, it should not be a problem - the only data that
> gets frequently updated being the database.
> regards,
> Razique
>
> *Nuage & Co - Razique Mahroua** *
> razique.mahr...@gmail.com
>
>
> Le 21 nov. 2012 à 15:51, Dave Spano  a écrit :
>
> JuanFra,
>
> I do use cephfs in production, but not for the /var/lib/instances
> directory. I do host the openstack database and the openstack configuration
> files on it for an HA cloud controller cluster, but I am probably crazier
> than most people, and I have a very small deployment. I currently have not
> had any problems with it, but due to the size of my cloud, I can afford to
> be very hands-on with it.
>
> The reason I have not hosted the /var/lib/instances directory is due to
> the fact that the data gets a lot more activity than my small database
> does. Instead, I prefer to perform block migrations rather than live ones
> until cephfs becomes more stable.
>
> Dave Spano
> Optogenics
> Systems Administrator
>
>
> --
> *From: *"Sébastien Han" 
> *To: *"JuanFra Rodríguez Cardoso" 
> *Cc: *"Openstack" , "ceph-devel" <
> ceph-de...@vger.kernel.org>
> *Sent: *Wednesday, November 21, 2012 4:03:48 AM
> *Subject: *Re: [Openstack] Ceph + Nova
>
> Hi,
>
> I don't think it's the best place to ask your question since it's not
> directly related to OpenStack but more about Ceph. I just put in c/c
> the ceph ML. Anyway, CephFS is not ready yet for production but I
> heard that some people use it. People from Inktank (the company behind
> Ceph) don't recommend it, AFAIR they expect something more production
> ready for Q2 2013. You can use it (I did, for testing purpose) but
> it's at your own risk.
> Beside of this RBD and RADOS are robust and stable now, so you can go
> with the Cinder and Glance integration without any problems.
>
> Cheers!
>
> On Wed, Nov 21, 2012 at 9:37 AM, JuanFra Rodríguez Cardoso
>  wrote:
> > Hi everyone:
> >
> > I'd like to know your opinion as nova experts:
> >
> > Would you recommend CephFS as shared storage in /var/lib/nova/instances?
> > Another option it would be use GlusterFS or MooseFS for
> > /var/lib/nova/instances directory and Ceph RBD for Glance and Nova
> volumes,
> > don't you think?
> >
> > Thanks for your attention.
> >
> > Best regards,
> > JuanFra
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.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] Folsom with VlanManager

[Sébastien Han]

Ah ok, I barely started with Diablo and quickly moved to Essex so I didn't
know ;-). Thanks for the input :)

Cheers!


On Wed, Nov 21, 2012 at 10:04 AM, Razique Mahroua  wrote:

> Even Diablo and Cactus before that I might say Seb :)
>
> *Nuage & Co - Razique Mahroua** *
> razique.mahr...@gmail.com
>
>
> Le 21 nov. 2012 à 09:56, Sébastien Han  a écrit :
>
> AFAIR it was also the case with Essex.
>
> Cheers!
>
>
> On Wed, Nov 21, 2012 at 9:46 AM, Razique Mahroua <
> razique.mahr...@gmail.com> wrote:
>
>> I had the same issue at first, but Vish is right, once you start spawning
>> an instance, everything should be brought up
>>
>> Regards,
>> Razique
>>
>> *Nuage & Co - Razique Mahroua** *
>> razique.mahr...@gmail.com
>>
>>
>> Le 20 nov. 2012 à 23:54, Vishvananda Ishaya  a
>> écrit :
>>
>> The vlans and bridges are not created until you run an instance in a
>> project The network is only assigned to a project when it is first needed
>> and the vlans and bridges are only created when an instance is launched on
>> a host in that project.
>>
>> Vish
>>
>> On Nov 19, 2012, at 10:05 AM, Juris  wrote:
>>
>> Hi all,
>>
>> I'm trying to configure Folsom to work with nova-networks and VlanManager
>> and it doesn't work.
>>
>> I can create networks with:
>> nova-manage network create --label testnet --fixed_range_v4 
>> 10.0.2.0/24--num_networks 1 --network_size 256 --vlan 200
>>
>> list them later:
>> nova-manage network list
>> 1 10.0.2.0/24   None   10.0.2.3   None   None
>>   200 None
>> 32692942-8965-4174-a45a-18cda4c7d183
>>
>> and there are no errors in /var/log/nova/*
>>
>> However, I can't see any bridges and vlan interfaces if I run ip addr or 
>> brctl
>> show.
>>
>> networking section of nova.conf looks like this:
>> network_manager=nova.network.manager.VlanManager
>> force_dhcp_release=True
>> dhcpbridge_flagfile=/etc/nova/nova.conf
>> dhcpbridge=/usr/bin/nova-dhcpbridge
>> firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
>> public_interface=eth0
>> vlan_interface=eth1
>> fixed_range=10.0.0.0/24
>> flat_network_dhcp_start=10.0.0.10
>> network_size=256
>> flat_injected=False
>> multi_host=True
>> send_arp_for_ha=True
>> connection_type=libvirt
>>
>> it's a pretty standard config and I can't see why it is not working.
>>
>> Any help will be much appreciated.
>>
>> Thank you in advance,
>> Juris
>> ___
>> 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
>>
>>
>
>
<>___
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] OpenStack Controller failover

[Sébastien Han]

Hi,

For the cloud controller, use 2 machines with a pacemaker setup with those
resource agents. Simple as that.
We have 2 branches, one for Essex and one for Folsom.

https://github.com/madkiss/openstack-resource-agents

Cheers!


On Wed, Nov 21, 2012 at 9:59 AM, Razique Mahroua
wrote:

> Hey Edwards,
> that is a concern many arise, today, there is not any both answer and
> implementations that would allow you to setup such.
> One approach is to work with stateless instances - using an orchestration
> tool such a Puppet of Chef, which would take care by itself of the spawning
> and restoration. It supposes to relegate all the data to the orchestration
> tool. In case a node fails, or even an instance - redeploying would take
> less time.
> I myself encountered though some customers topology which don't fit such
> approach (critical databases, etc...) for such case, you can either prep. a
> sleeping instance in one another node or setup a data replication between X
> instances. Network-wise you can automate the floating ip allocation using a
> detection solution.
> I think that feature (auto respawn) would come up soon (guys feel free to
> correct me), since this is a real concern.
> Regards,
> Razique
>
> *Nuage & Co - Razique Mahroua** *
> razique.mahr...@gmail.com
>
>
> Le 21 nov. 2012 à 08:51,  a écrit :
>
> Dear
> I find H.A for openstack nova-network
>
> http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html
> 
>
> Openstack instance support NFS migrate by all compute node.
> Swift have Zone and backup objects.
> MySql have Cluster.
>
> How about all openstack H.A or Failover?
> If Openstack controller physical machine crash.
> (Dashboard, nova-api, nova information, glance, keystone, etc…)
> All service will disappear.
> Could we recover openstack controller automatically?
>
> Thanks all.
>
> Edward
> ___
> 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] Ceph + Nova

[Sébastien Han]

Hi,

I don't think it's the best place to ask your question since it's not
directly related to OpenStack but more about Ceph. I just put in c/c
the ceph ML. Anyway, CephFS is not ready yet for production but I
heard that some people use it. People from Inktank (the company behind
Ceph) don't recommend it, AFAIR they expect something more production
ready for Q2 2013. You can use it (I did, for testing purpose) but
it's at your own risk.
Beside of this RBD and RADOS are robust and stable now, so you can go
with the Cinder and Glance integration without any problems.

Cheers!

On Wed, Nov 21, 2012 at 9:37 AM, JuanFra Rodríguez Cardoso
 wrote:
> Hi everyone:
>
> I'd like to know your opinion as nova experts:
>
> Would you recommend CephFS as shared storage in /var/lib/nova/instances?
> Another option it would be use GlusterFS or MooseFS for
> /var/lib/nova/instances directory and Ceph RBD for Glance and Nova volumes,
> don't you think?
>
> Thanks for your attention.
>
> Best regards,
> JuanFra
>
> ___
> 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] Folsom with VlanManager

[Sébastien Han]

AFAIR it was also the case with Essex.

Cheers!


On Wed, Nov 21, 2012 at 9:46 AM, Razique Mahroua
wrote:

> I had the same issue at first, but Vish is right, once you start spawning
> an instance, everything should be brought up
>
> Regards,
> Razique
>
> *Nuage & Co - Razique Mahroua** *
> razique.mahr...@gmail.com
>
>
> Le 20 nov. 2012 à 23:54, Vishvananda Ishaya  a
> écrit :
>
> The vlans and bridges are not created until you run an instance in a
> project The network is only assigned to a project when it is first needed
> and the vlans and bridges are only created when an instance is launched on
> a host in that project.
>
> Vish
>
> On Nov 19, 2012, at 10:05 AM, Juris  wrote:
>
> Hi all,
>
> I'm trying to configure Folsom to work with nova-networks and VlanManager
> and it doesn't work.
>
> I can create networks with:
> nova-manage network create --label testnet --fixed_range_v4 
> 10.0.2.0/24--num_networks 1 --network_size 256 --vlan 200
>
> list them later:
> nova-manage network list
> 1 10.0.2.0/24   None   10.0.2.3   None   None
>   200 None
> 32692942-8965-4174-a45a-18cda4c7d183
>
> and there are no errors in /var/log/nova/*
>
> However, I can't see any bridges and vlan interfaces if I run ip addr or brctl
> show.
>
> networking section of nova.conf looks like this:
> network_manager=nova.network.manager.VlanManager
> force_dhcp_release=True
> dhcpbridge_flagfile=/etc/nova/nova.conf
> dhcpbridge=/usr/bin/nova-dhcpbridge
> firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
> public_interface=eth0
> vlan_interface=eth1
> fixed_range=10.0.0.0/24
> flat_network_dhcp_start=10.0.0.10
> network_size=256
> flat_injected=False
> multi_host=True
> send_arp_for_ha=True
> connection_type=libvirt
>
> it's a pretty standard config and I can't see why it is not working.
>
> Any help will be much appreciated.
>
> Thank you in advance,
> Juris
> ___
> 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
>
>
___
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] Allocate specific floating IP to an instance

[Sébastien Han]

Thanks for the detail reply :-).

And many thanks for the patch, I'll give a try and let you know.

Cheers!


On Tue, Oct 30, 2012 at 12:47 PM, Kiall Mac Innes  wrote:
> P.S. - That patch is against the current "stable/folsom" branch.. It won't
> apply to Grizzly cleanly..
>
> Thanks,
> Kiall
>
>
>
> On Tue, Oct 30, 2012 at 11:46 AM, Kiall Mac Innes 
> wrote:
>>
>> Response inline.
>>
>> Thanks,
>> Kiall
>>
>>
>> On Tue, Oct 30, 2012 at 11:04 AM, Sébastien Han 
>> wrote:
>>>
>>> Hi Kial,
>>>
>>> Hold on...
>>> You obviously didn't understand my question. So please don't try to
>>> teach me anything. I can admit that the initial description of my
>>> request was a bit unclear. So I'm gonna try to clarify it.
>>
>>
>> I apologize, I certainly did not intend any insult.
>>
>>>
>>>
>>> I use nova-network with the VLAN manager, so I have a network range
>>> per projects (fixed ips), per VLAN. Each project uses a specific pool,
>>> I use the floating IPs to expose instances to another private network
>>> and I don't use the "auto_assign_floating_ip" parameter.
>>
>>
>> Great - Sounds like a pretty standard setup.
>>
>>>
>>>
>>> Now, when I perform a "nova floating-ip-create " this gives
>>> me the first floating IP available of that pool. What I want to
>>> know/achieve is to decide the floating IP address to create. Basically
>>> this could lead to a command like:
>>>
>>> # nova floating-ip-create 
>>> 
>>
>>
>> Ah - I understand now.
>>
>> This is not supported by Nova Network (I can't say if it's supported with
>> Quantum).
>>
>>>
>>>
>>> But as you can see below, it's not available from the CLI:
>>>
>>> # nova help floating-ip-create
>>> usage: nova floating-ip-create []
>>>
>>> Allocate a floating IP for the current tenant.
>>>
>>> Positional arguments:
>>> Name of Floating IP Pool. (Optional)
>>>
>>> Then I'll associate this floating IP to one of my instances.
>>>
>>> Let's try to raise the level of this discussion. Now if there is
>>> something that I don't know, or something that I missed, feel free to
>>> teach/correct me.
>>
>>
>> Again - I apologize. No insult was intended.
>>
>>>
>>> I'm looking for a workaround, or code patch.
>>> Something that doesn't require huge amount of work. Is that doable?
>>
>>
>> I believe it is doable without significant changes to the code.
>>
>> By patching the code to allow an extra parameter to pass through from the
>> REST API call, all the way through to the DB's allocation method, the
>> allocation method could be made to choose a particular IP by altering the
>> SQL query executed.
>>
>> Some pointers to the relevant parts of the code:
>>
>> REST API:
>>
>> https://github.com/openstack/nova/blob/stable/folsom/nova/api/openstack/compute/contrib/floating_ips.py#L162-180
>>
>> Network Service API:
>>
>> https://github.com/openstack/nova/blob/stable/folsom/nova/network/api.py#L177-188
>>
>> Network Service Manager:
>>
>> https://github.com/openstack/nova/blob/stable/folsom/nova/network/manager.py#L406-443
>>
>> DB API:
>>
>> https://github.com/openstack/nova/blob/stable/folsom/nova/db/api.py#L263-269
>>
>> DB Implementation:
>>
>> https://github.com/openstack/nova/blob/stable/folsom/nova/db/sqlalchemy/api.py#L700-718
>>
>> I hope this helps!
>>
>> Actually - It looked like it could be done fairly quickly, you can try
>> this (untested) patch: http://paste.ubuntu.com/1317723/plain/
>>
>> Once applied, you should be able to supply an "ip" param as part of the
>> REST API call, and you will get that specific IP - if it is available. This
>> doesn't update the CLI, I've never looked at it's code so wouldn't know
>> where to start :)
>>
>> Thanks,
>> Kiall
>>
>>>
>>> Anyone?
>>>
>>> On Tue, Oct 30, 2012 at 11:03 AM, Kiall Mac Innes 
>>> wrote:
>>> > Hi Sebastian,
>>> >
>>> > The commands are nearly identical - just replace quantum with nova!
>>> >
>>> > Although, it sounds like you already have floating IP

Re: [Openstack] Allocate specific floating IP to an instance

[Sébastien Han]

Hi Kial,

Hold on...
You obviously didn't understand my question. So please don't try to
teach me anything. I can admit that the initial description of my
request was a bit unclear. So I'm gonna try to clarify it.

I use nova-network with the VLAN manager, so I have a network range
per projects (fixed ips), per VLAN. Each project uses a specific pool,
I use the floating IPs to expose instances to another private network
and I don't use the "auto_assign_floating_ip" parameter.

Now, when I perform a "nova floating-ip-create " this gives
me the first floating IP available of that pool. What I want to
know/achieve is to decide the floating IP address to create. Basically
this could lead to a command like:

# nova floating-ip-create  

But as you can see below, it's not available from the CLI:

# nova help floating-ip-create
usage: nova floating-ip-create []

Allocate a floating IP for the current tenant.

Positional arguments:
Name of Floating IP Pool. (Optional)

Then I'll associate this floating IP to one of my instances.

Let's try to raise the level of this discussion. Now if there is
something that I don't know, or something that I missed, feel free to
teach/correct me. I'm looking for a workaround, or code patch.
Something that doesn't require huge amount of work. Is that doable?

Anyone?

On Tue, Oct 30, 2012 at 11:03 AM, Kiall Mac Innes  wrote:
> Hi Sebastian,
>
> The commands are nearly identical - just replace quantum with nova!
>
> Although, it sounds like you already have floating IPs being allocated
> randomly.
>
> That could be one of two things - either you have
> auto_assign_floatingip=True in your configuration, or you misunderstand the
> difference between fixed and floating ips.
>
> When you boot an instance, does it get a private or public IP? And - when
> you ran the network-create command, what IP range did you use?
>
> Kiall
>
> On Oct 30, 2012 9:26 AM, "Sébastien Han"  wrote:
>>
>> @Kiall, if it does, tell us more about it please.
>>
>>
>> On Tue, Oct 30, 2012 at 10:19 AM, Kiall Mac Innes 
>> wrote:
>> > I'm fairly confident that quantum is not a requirement for this.
>> >
>> > Nova's in-built networking supports exactly this since as long ago as I
>> > can
>> > remember.
>> >
>> > Thanks,
>> > Kiall
>> >
>> > On Oct 30, 2012 9:04 AM, "Emilien Macchi"  wrote:
>> >>
>> >> Hello Sebastien,
>> >>
>> >>
>> >> What you can do today is to choose manually which floating IP you need
>> >> to
>> >> associate with a specific instance.
>> >> You need to run OpenStack Folsom + Quantum.
>> >>
>> >> First, you need to create Floating IP pool(s) from Quantum CLI, and
>> >> after
>> >> that, the tenant is able to associate this IP to a private instance :
>> >>
>> >> quantum floatingip-create ext_net
>> >>
>> >> quantum floatingip-associate $FLOATING_ID $PORT_ID
>> >>
>> >> More informations about Networking configuration with Quantum CLI here
>> >> :
>> >>
>> >>
>> >> http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html
>> >>
>> >>
>> >> Cheers ;-)
>> >>
>> >>
>> >> Emilien Macchi
>> >> 
>> >> // eNovance Inc.  http://enovance.com
>> >> // ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80
>> >> // 10 rue de la Victoire 75009 Paris
>> >>
>> >> 
>> >> De: "Sébastien Han" 
>> >> À: "Openstack" 
>> >> Envoyé: Lundi 29 Octobre 2012 17:25:47
>> >> Objet: [Openstack] Allocate specific floating IP to an instance
>> >>
>> >> Hi Stacker,
>> >>
>> >> I know OpenStack is not designed that way and I don't think it's
>> >> possible (or maybe I misses something :)) but I was wondering if there
>> >> is any simple workaround to choose a specific floating IP to allocate.
>> >> In other words, don't give me a random or N+1 next floating IP
>> >> available but let me decide which floating IP I want to assign to my
>> >> instance. It doesn't make sense in a public cloud but it does for a
>> >> corporate/private cloud. It would be nice to have :)
>> >>
>> >> Thanks in advance.
>> >>
>> >> Cheers!
>> >>
>> >> ___
>> >> 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] Allocate specific floating IP to an instance

[Sébastien Han]

@Kiall, if it does, tell us more about it please.


On Tue, Oct 30, 2012 at 10:19 AM, Kiall Mac Innes  wrote:
> I'm fairly confident that quantum is not a requirement for this.
>
> Nova's in-built networking supports exactly this since as long ago as I can
> remember.
>
> Thanks,
> Kiall
>
> On Oct 30, 2012 9:04 AM, "Emilien Macchi"  wrote:
>>
>> Hello Sebastien,
>>
>>
>> What you can do today is to choose manually which floating IP you need to
>> associate with a specific instance.
>> You need to run OpenStack Folsom + Quantum.
>>
>> First, you need to create Floating IP pool(s) from Quantum CLI, and after
>> that, the tenant is able to associate this IP to a private instance :
>>
>> quantum floatingip-create ext_net
>>
>> quantum floatingip-associate $FLOATING_ID $PORT_ID
>>
>> More informations about Networking configuration with Quantum CLI here :
>>
>> http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html
>>
>>
>> Cheers ;-)
>>
>>
>> Emilien Macchi
>> 
>> // eNovance Inc.  http://enovance.com
>> // ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80
>> // 10 rue de la Victoire 75009 Paris
>>
>> 
>> De: "Sébastien Han" 
>> À: "Openstack" 
>> Envoyé: Lundi 29 Octobre 2012 17:25:47
>> Objet: [Openstack] Allocate specific floating IP to an instance
>>
>> Hi Stacker,
>>
>> I know OpenStack is not designed that way and I don't think it's
>> possible (or maybe I misses something :)) but I was wondering if there
>> is any simple workaround to choose a specific floating IP to allocate.
>> In other words, don't give me a random or N+1 next floating IP
>> available but let me decide which floating IP I want to assign to my
>> instance. It doesn't make sense in a public cloud but it does for a
>> corporate/private cloud. It would be nice to have :)
>>
>> Thanks in advance.
>>
>> Cheers!
>>
>> ___
>> 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] Allocate specific floating IP to an instance

[Sébastien Han]

Bonjour Mr Macchi,

As you may already know I don't run Quantum but nova-network with Folsom.
However I should have mentioned it before :)

Any trick for nova-network?

Cheers!

On Tue, Oct 30, 2012 at 10:03 AM, Emilien Macchi  wrote:
> Hello Sebastien,
>
>
> What you can do today is to choose manually which floating IP you need to
> associate with a specific instance.
> You need to run OpenStack Folsom + Quantum.
>
> First, you need to create Floating IP pool(s) from Quantum CLI, and after
> that, the tenant is able to associate this IP to a private instance :
>
> quantum floatingip-create ext_net
> quantum floatingip-associate $FLOATING_ID $PORT_ID
>
> More informations about Networking configuration with Quantum CLI here :
> http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html
>
>
> Cheers ;-)
>
>
> Emilien Macchi
> 
> // eNovance Inc.  http://enovance.com
> // ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80
> // 10 rue de la Victoire 75009 Paris
>
> 
> De: "Sébastien Han" 
> À: "Openstack" 
> Envoyé: Lundi 29 Octobre 2012 17:25:47
> Objet: [Openstack] Allocate specific floating IP to an instance
>
>
> Hi Stacker,
>
> I know OpenStack is not designed that way and I don't think it's
> possible (or maybe I misses something :)) but I was wondering if there
> is any simple workaround to choose a specific floating IP to allocate.
> In other words, don't give me a random or N+1 next floating IP
> available but let me decide which floating IP I want to assign to my
> instance. It doesn't make sense in a public cloud but it does for a
> corporate/private cloud. It would be nice to have :)
>
> Thanks in advance.
>
> Cheers!
>
> ___
> 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] Allocate specific floating IP to an instance

[Sébastien Han]

Hi Stacker,

I know OpenStack is not designed that way and I don't think it's
possible (or maybe I misses something :)) but I was wondering if there
is any simple workaround to choose a specific floating IP to allocate.
In other words, don't give me a random or N+1 next floating IP
available but let me decide which floating IP I want to assign to my
instance. It doesn't make sense in a public cloud but it does for a
corporate/private cloud. It would be nice to have :)

Thanks in advance.

Cheers!

___
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] Special Zero Size root in Flavor, what exactly does it mean?

[Sébastien Han]

Hi,

If you use 0 for the rootfs. It means that your vm uses the virtual
size of the based image. You can check the virtual size with qemu.

# qemu-img info 

Cheers!

On Sat, Oct 27, 2012 at 11:08 PM, Jonathan Proulx  wrote:
> Hi All,
>
> I know that specifying a zero size root volume in a flavor is
> "special" but what exactly does it mean.  I'm writing up some
> documentation on flavors and realized I can't fully explain the
> default m1.tiny ...
>
> Thanks,
> -Jon
>
> ___
> 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] OpenStack devroom for FOSDEM 2013

[Sébastien Han]

I'll be glad to offer my help as well.
You can include me into this discussion.

Cheers!


On Mon, Oct 22, 2012 at 5:13 PM, Thierry Carrez  wrote:
> Thierry Carrez wrote:
>> So this year around, to simplify organization I thought we would ask for
>> a one-day "openstack" devroom, which could be merged with other "open
>> source cloud computing" projects into a single devroom, if need be.
>
> I just got the confirmation that we'll have a common "Cloud" devroom at
> FOSDEM 2013. It will be all day on Sunday, February 3rd in the Chavanne
> auditorium (550 seats) and it will be a common devroom with other open
> source cloud infrastructure projects.
>
> I know Russell and Jasper volunteered to help organizing. If anyone else
> is interested, let me know so that I include you in the early
> discussions about co-organizing this devroom.
>
> Regards,
>
> --
> Thierry Carrez (ttx)
> Release Manager, OpenStack
>
> ___
> 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] Cloudpipe broken in Folsom?

[Sébastien Han]

Hi Stackers!

I tried to setup the cloudpipe VPN with Folsom. I followed the
official doc. Did I make something wrong?

Just opened a bug on launchpad about it.

https://bugs.launchpad.net/nova/+bug/1069573

Any idea?

Cheers!

___
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] glance add image using curl

[Sébastien Han]

Hi,

glance add is a deprecated command, use glance image-create instead.

When you want to reproduce the API request, you can always use -d arg
to enter in debug mode and see the API request translation.

For glance, you have something like (this is what I got from the -d option):

curl -i -X POST -H 'x-image-meta-container_format: ami' -H
'User-Agent: python-glanceclient' -H 'x-image-meta-size: 1049624576'
-H 'x-image-meta-is_public: True' -H 'X-Auth-Token:
80ce0867325f4ad9b1ebe6b17990bf28' -H 'Content-Type:
application/octet-stream' -H 'x-image-meta-disk_format: ami' -H
'x-image-meta-name: test' -d '' http://IP_glance_registry_endpoint:9292/v1/images

hope it helps!

cheers!

On Thu, Oct 18, 2012 at 9:21 AM, Matthieu Simonin
 wrote:
> Hi,
>
> The API doc about glance api says that a post request to
> "http://glance/v1/images";.
> How can I perform that ? Especially, I don't understant how i specify the
> image I want to upload in the registry in the post request.
>
> I have no problem using glance client (glance add) but i don't understand
> how to perform the same action using curl.
>
> Bye,
>
> Matt
>
>
>
>
> ___
> 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] How can I choose my own timezone on Dashboard of Essex?

[Sébastien Han]

Hi,

There is a line in /etc/openstack-dashboard/local_settings.py called
TIME_ZONE

# The timezone of the server. This should correspond with the timezone
# of your entire OpenStack installation, and hopefully be in UTC.
TIME_ZONE = "UTC"

Change it, restart apache and memcached, that should do the trick.

Have you looked at that?

Cheers!

On Thu, Oct 11, 2012 at 7:38 AM, Ray Sun  wrote:

> In the Dashboard of Essex version, seems the datetime is always displayed
> as UTC time, How can I choose my own timezone?
> Thanks.
>
> - Ray
> Yours faithfully, Kind regards.
>
> CIeNET Technologies (Beijing) Co., Ltd
> Email: qsun01...@cienet.com.cn
> Office Phone: +86-01081470088-7079
> Mobile Phone: +86-18901118291
>
>
> ___
> 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] Can't update the metadata via nova cli

[Sébastien Han]

Thank you very much for those clarifications :D


On Fri, Aug 10, 2012 at 12:31 AM, Vishvananda Ishaya
wrote:

>
> On Aug 9, 2012, at 1:56 PM, Sébastien Han  wrote:
>
>
> Did I miss something?
>
>
>  Unfortunately this is confusing because the term metadata is used for two
> different things.
>
> the metadata visible to the instance is a replication of the aws metadata
> server. it is constructed from the database (mostly the instances table)
>
> The metadata you were setting with your command are sets of keys and
> values that are visible in the compute api:
>
>
> http://docs.openstack.org/trunk/openstack-compute/developer/openstack-compute-api-1.1/content/MetadataSection.html
>
> which is stored in the instance_metadata table
>
>
> Last question, is there a way to update the metadata of a running
> instance. I mean instead of updating the db record... For example
> re-injecting a SSH key?
>
>
> no, there is currently no way of doing this through the api.
>
> Vish
>
___
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] [OpenStack][Nova] Question regarding multiple network interfaces

[Sébastien Han]

If your eth0 (public interface) can access Internet, with the ip_forward
your instance should be able too...


On Wed, Aug 8, 2012 at 12:05 PM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> So i have set up a small proof of concept, one controller node and two
> compute nodes. Since the switches do not support VLAN i'm using flat dhcp.
> Each machine has two network interfaces. Eth0 is connected to the public
> switch and eth1 to the private switch. The private switch has no access to
> the internet.
>
> Both compute nodes have the value of cat /proc/sys/net/ipv4/ip_forward set
> to 1. However, i still can't make an instance connect to the outside.
>
>  Any thoughts?
> On Tue, Aug 7, 2012 at 11:32 PM, Sébastien Han wrote:
>
>> It's part of the operating system
>>
>> # echo 1 > /proc/sys/net/ipv4/ip_forward
>>
>> Then edit your /etc/sysctl.conf and uncomment net.ipv4.ip_forward=1 to
>> make this persistent after reboot.
>>
>> Finally run --> # sysctl -p
>>
>> That's all, cheers!
>>
>>
>> On Tue, Aug 7, 2012 at 11:50 PM, Leander Bessa Beernaert
>>  wrote:
>> > Is there a flag in the nova.conf file or is this something that needs
>> to be
>> > done on the operating system?
>> >
>> >
>> > On Tue, Aug 7, 2012 at 8:26 PM, Sébastien Han 
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> If eth0 is connected to the public switch and if eth1 is connected to
>> >> the private switch you can enable the ipv4 forwarding on the compute
>> >> node. Thanks to this the VMs will have access to the outside world and
>> >> the packet will be routed from eth1 to eth0 :).
>> >>
>> >> Cheers!
>> >>
>> >> On Tue, Aug 7, 2012 at 5:18 PM, Leander Bessa Beernaert
>> >>  wrote:
>> >> > Hello,
>> >> >
>> >> > I have a question regarding the use of two network interfaces.
>> According
>> >> > to
>> >> > the official documentation, one of the interfaces is used for public
>> >> > access
>> >> > and the other for internal access (inter-vm communication). What i'd
>> >> > like to
>> >> > know is how does an instance connect to the outside world (internet
>> >> > access)?
>> >> > Is it done through the switch connected to the private interface or
>> the
>> >> > public interface?
>> >> >
>> >> > --
>> >> > Cumprimentos / Regards,
>> >> > Leander
>> >> >
>> >> > ___
>> >> > Mailing list: https://launchpad.net/~openstack
>> >> > Post to : openstack@lists.launchpad.net
>> >> > Unsubscribe : https://launchpad.net/~openstack
>> >> > More help   : https://help.launchpad.net/ListHelp
>> >> >
>> >
>> >
>> >
>> >
>> > --
>> > Cumprimentos / Regards,
>> > Leander
>>
>
>
>
> --
> Cumprimentos / Regards,
> Leander
>
___
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] Can't update the metadata via nova cli

[Sébastien Han]

Hi everyone,

I tried a little today.

$ nova meta my_instance set hostname=new_hostname

I didn't get any errors.

Nothing in the instance (curl
http://169.254.169.254/latest/meta-data/hostname) even after reboot and
nothing in the instance db record.

Here are the nova-api trace, seems to be ok:

2012-08-07 15:18:58 INFO nova.api.openstack.wsgi
[req-c8bf2011-933b-4d6a-b28c-48063252fbf1 359076e3189b4658a4dd1b83d6313cc9
5172f50226f647ebb03ca4e4e82d056d] POST
http://172.17.1.2:8774/v2/5172f50226f647ebb03ca4e4e82d056d/servers/4e1c4652-199c-4160-9a73-2eddcf4cd21f/action
2012-08-07 15:18:59 INFO nova.api.openstack.wsgi
[req-c8bf2011-933b-4d6a-b28c-48063252fbf1 359076e3189b4658a4dd1b83d6313cc9
5172f50226f647ebb03ca4e4e82d056d]
http://172.17.1.2:8774/v2/5172f50226f647ebb03ca4e4e82d056d/servers/4e1c4652-199c-4160-9a73-2eddcf4cd21f/actionreturned
with HTTP 200

Did I miss something?

Last question, is there a way to update the metadata of a running instance.
I mean instead of updating the db record... For example re-injecting a SSH
key?

Cheers!
___
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 on dnsmasq

[Sébastien Han]

Hi guys,

Any ideas on this?

https://bugs.launchpad.net/nova/+bug/1033675

https://answers.launchpad.net/nova/+question/205136

Any advice/tip will be truly appreciated :)

Cheers!
___
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] [OpenStack][Nova] Question regarding multiple network interfaces

[Sébastien Han]

It's part of the operating system

# echo 1 > /proc/sys/net/ipv4/ip_forward

Then edit your /etc/sysctl.conf and uncomment net.ipv4.ip_forward=1 to
make this persistent after reboot.

Finally run --> # sysctl -p

That's all, cheers!


On Tue, Aug 7, 2012 at 11:50 PM, Leander Bessa Beernaert
 wrote:
> Is there a flag in the nova.conf file or is this something that needs to be
> done on the operating system?
>
>
> On Tue, Aug 7, 2012 at 8:26 PM, Sébastien Han 
> wrote:
>>
>> Hi,
>>
>> If eth0 is connected to the public switch and if eth1 is connected to
>> the private switch you can enable the ipv4 forwarding on the compute
>> node. Thanks to this the VMs will have access to the outside world and
>> the packet will be routed from eth1 to eth0 :).
>>
>> Cheers!
>>
>> On Tue, Aug 7, 2012 at 5:18 PM, Leander Bessa Beernaert
>>  wrote:
>> > Hello,
>> >
>> > I have a question regarding the use of two network interfaces. According
>> > to
>> > the official documentation, one of the interfaces is used for public
>> > access
>> > and the other for internal access (inter-vm communication). What i'd
>> > like to
>> > know is how does an instance connect to the outside world (internet
>> > access)?
>> > Is it done through the switch connected to the private interface or the
>> > public interface?
>> >
>> > --
>> > Cumprimentos / Regards,
>> > Leander
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~openstack
>> > Post to : openstack@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~openstack
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>
>
>
>
> --
> Cumprimentos / Regards,
> Leander

___
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] [OpenStack][Nova] Question regarding multiple network interfaces

[Sébastien Han]

Hi,

If eth0 is connected to the public switch and if eth1 is connected to
the private switch you can enable the ipv4 forwarding on the compute
node. Thanks to this the VMs will have access to the outside world and
the packet will be routed from eth1 to eth0 :).

Cheers!

On Tue, Aug 7, 2012 at 5:18 PM, Leander Bessa Beernaert
 wrote:
> Hello,
>
> I have a question regarding the use of two network interfaces. According to
> the official documentation, one of the interfaces is used for public access
> and the other for internal access (inter-vm communication). What i'd like to
> know is how does an instance connect to the outside world (internet access)?
> Is it done through the switch connected to the private interface or the
> public interface?
>
> --
> Cumprimentos / Regards,
> Leander
>
> ___
> 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] KVM live block migration: stability, future, docs

[Sébastien Han]

Hi!

I think it's a pretty useful feature, a good compromise. As you said using
a shared fs implies a lot of things and can dramatically decrease your
performance rather than using the local fs. I tested it and I will use it
for my deployment. I'll be happy to discuss more deeply with you about this
feature :)

I also feel a little concern about this statement:

 It don't work so well, it complicates migration code, and we are building
> a replacement that works.


I have to go further with my tests, maybe we could share some ideas, use
case etc...

Cheers!

On Mon, Aug 6, 2012 at 3:08 PM, Blair Bethwaite 
wrote:
> Hi all,
>
> KVM block migration support in OpenStack
> (https://blueprints.launchpad.net/nova/+spec/kvm-block-migration)
> seems to be somewhat of a secret - there's almost nothing in the
> docs/guides (which to the contrary state that live migration is only
> possible with shared storage) and only a couple of mentions on list,
> yet it's been around since Diablo. Should this be taken to mean it's
> considered unstable, or just that no-one interested in documenting it
> understands the significance of such a feature to deployment
> architects? After all, decent shared storage is an expensive prospect
> with a pile of associated design and management overhead!
>
> I'd be happy to contribute some documentation patches (starting with
> the admin guide) that cover this. But first I'd like to get some
> confirmation that it's here to stay, which will be significant for our
> own large deployment. We've tested with Essex on Ubuntu Precise and
> seen a bit of weird file-system behaviour, which we currently suspect
> might be a consequence of using ext3 in the guest. But also, there
> seems to be some associated lag with interactive services (e.g. active
> VNC session) in the guest, not yet sure how this compares to the
> non-block live migration case.
>
> We'd really appreciate anybody actively using this feature to speak up
> and comment on their mileage, especially with respect to ops.
>
> I'm slightly concerned that KVM may drop this going forward
> (http://www.spinics.net/lists/kvm/msg72228.html), though that would be
> unlikely to affect anybody deploying on Precise.
>
> --
> Cheers,
> ~Blairo
>
> ___
> 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] Change Ephemeral Disk FS

[Sébastien Han]

Oh I didn't know that one!
Thanks ;)


On Mon, Aug 6, 2012 at 6:07 PM, Vishvananda Ishaya wrote:

> No need to edit code, there is a config option for this:
>
> ## (MultiStrOpt) mkfs commands for ephemeral device. The format is
> =
>
> Put the following in nova.conf:
>
> virt_mkfs=default=mkfs.ext4 -L %(fs_label)s -F %(target)s
>
>
> On Aug 6, 2012, at 3:02 AM, Sébastien Han  wrote:
>
> Hi,
>
> I think this only way is to edit the code like so:
>
>- go to the line 66
>of /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py
>- and change to  'default=mkfs.ext4 -L %(fs_label)s -F %(target)s',
>
> Make sure to purge your /var/lib/nova/instances/_base
> It worked for me :)
>
> Let me know if it's ok :)
>
> Cheers!
>
>
> On Mon, Aug 6, 2012 at 10:47 AM, Jerico Revote 
> wrote:
>
>> Hi,
>>
>> Is there a way to change the default file system of the ephemeral disk
>> attached to an instance?
>> By default it's ext3.
>>
>> Thanks,
>>
>> Jerico
>> ___
>> 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] Change Ephemeral Disk FS

[Sébastien Han]

I'm using Essex.

Where did you make the code change?

You must put the change on each nova-compute node.

Enable the --verbose flag in nova.conf on your compute nodes,
purge  /var/lib/nova/instances/_base/'ephemeral_something', boot a new vm
and watch the log.
Grep for a line matching 'mkfs'

My logs:

nova.service [-] virt_mkfs : ['default=mkfs.ext4 -L %(fs_label)s -F
%(target)s', 'linux=mkfs.ext3 -L %(fs_label)s -F %(target)s',
'windows=mkfs.ntfs --force --fast --label %(fs_label)s %(target)s'] from
(pid=2343) wait /usr/lib/python2.7/dist-packages/nova/service.py:411
nova.utils [req-4559f0ea-df70-4d86-b61d-91d0798e3e93
359076e3189b4658a4dd1b83d6313cc9 5172f50226f647ebb03ca4e4e82d056d] Running
cmd (subprocess): mkfs.ext4 -L ephemeral0 -F
/var/lib/nova/instances/_base/ephemeral_0_20_None from (pid=2343) execute
/usr/lib/python2.7/dist-packages/nova/utils.py:219



On Mon, Aug 6, 2012 at 1:51 PM, Jerico Revote wrote:

> Hi,
>
> Are you using Essex or Folsom when it worked for you?
>
> Regards,
>
> Jerico
>
> On 06/08/2012, at 8:48 PM, Sébastien Han  wrote:
>
> Cool ;)
>
> On Mon, Aug 6, 2012 at 12:47 PM, Jerico Revote 
> wrote:
>
>> Thanks Sebastien, I'll give it a shot.
>>
>> Jerico
>>
>> On 06/08/2012, at 8:02 PM, Sébastien Han  wrote:
>>
>> Hi,
>>
>> I think this only way is to edit the code like so:
>>
>>- go to the line 66
>>of /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py
>>- and change to  'default=mkfs.ext4 -L %(fs_label)s -F %(target)s',
>>
>> Make sure to purge your /var/lib/nova/instances/_base
>> It worked for me :)
>>
>> Let me know if it's ok :)
>>
>> Cheers!
>>
>>
>> On Mon, Aug 6, 2012 at 10:47 AM, Jerico Revote 
>> wrote:
>>
>>> Hi,
>>>
>>> Is there a way to change the default file system of the ephemeral disk
>>> attached to an instance?
>>> By default it's ext3.
>>>
>>> Thanks,
>>>
>>> Jerico
>>> ___
>>> 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] Change Ephemeral Disk FS

[Sébastien Han]

Hi,

I think this only way is to edit the code like so:

   - go to the line 66
   of /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py
   - and change to  'default=mkfs.ext4 -L %(fs_label)s -F %(target)s',

Make sure to purge your /var/lib/nova/instances/_base
It worked for me :)

Let me know if it's ok :)

Cheers!


On Mon, Aug 6, 2012 at 10:47 AM, Jerico Revote wrote:

> Hi,
>
> Is there a way to change the default file system of the ephemeral disk
> attached to an instance?
> By default it's ext3.
>
> Thanks,
>
> Jerico
> ___
> 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] compute_nodes DB table

[Sébastien Han]

Hi,

The interval can be managed via the periodic_interval flag in nova.conf,
which is by default 60 sec

Cheers!


On Mon, Aug 6, 2012 at 9:40 AM, Trinath Somanchi  wrote:

> thanks a lot for the guidance...
>
>
>
> On Mon, Aug 6, 2012 at 12:57 PM, Michael Still <
> michael.st...@canonical.com> wrote:
>
>> On 06/08/12 16:47, Trinath Somanchi wrote:
>> > Hi-
>> >
>> > Can any one guide me on understanding the process that updates the
>> > compute_nodes table in nova database.
>>
>> nova-compute on each compute node sends a regular message to the
>> nova-scheduler on the scheduler node with an update of its status. These
>> are saved into that table. You can see these updates in your log:
>>
>> 2012-08-06 17:25:59 DEBUG nova.scheduler.host_manager
>> [req-4549b72e-83e5-4617-9a6b-81c17609c83e None None] Received compute
>> service update from molokai. from (pid=5003) update_service_capabilities
>> /usr/lib/python2.7/dist-packages/nova/scheduler/host_manager.py:273
>>
>> Cheers,
>> Mikal
>>
>
>
>
> --
> Regards,
> --
> Trinath Somanchi,
> +91 9866 235 130
>
>
> ___
> 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] A series of blog posts on OpenStack networking details

[Sébastien Han]

Hello,

Looks nice but I look forward to read the one about VLAN manager :D
Thanks!

Cheer!


On Fri, Aug 3, 2012 at 8:50 PM, Eugene Kirpichov wrote:

> Hello community,
>
> I'd like to advertise that me and my colleague Piotr Siwczak at
> Mirantis have started a series of blog posts explaining the gory
> details of OpenStack networking.
>
> http://www.mirantis.com/tag/networking/
>
> So far we have two posts:
>
>
> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/
> - basics of FlatManager and FlatDHCPManager in multi-host mode.
>
>
> http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
> - extremely detailed account of FlatDHCPManager in single-host mode;
> down to a walkthrough of L2 packet flow for several scenarios. I wrote
> this post in revenge for my own struggles when I dreamt "if only
> someone had described in extreme detail how it is *supposed* to work"
> but was not able to find anything like that :)
>
> A few more will appear soon: two posts from Piotr on VLANManager,
> eventually also analyzing the packet flow.
>
> (me and Peter have slightly different styles: he prefers to cover
> details across several posts while I prefer to write a huge post with
> all the details at once)
>
> Comments and especially corrections are extremely welcome! [and, well,
> shares too :) ]
>
> --
> Eugene Kirpichov
> http://www.linkedin.com/in/eugenekirpichov
>
> ___
> 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] how to create different instance name when create more instance in same time

[Sébastien Han]

You can always rename them with the dashboard, but this doesn't mean that
the hostname will change... It will remain the same for every VMs.


On Thu, Aug 2, 2012 at 9:31 AM, Shake Chen  wrote:

> Hi
>
> Now I try to create more instance in same time in Dashobard. but the
> Instance name is same. how to sovle it?
>
>
>
> --
> Shake Chen
>
>
>
> ___
> 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] Virtual machines are not getting ip

[Sébastien Han]

Are you using multi_host option?

What is your nova network manager?

More info about your setup could be useful...


On Wed, Aug 1, 2012 at 9:25 AM, Alessandro Tagliapietra <
tagliapietra.alessan...@gmail.com> wrote:

> Hello,
>
> please help, this thing is getting me crazy. The vm starts fine but i get:
>
> > cloud-init-nonet waiting 120 seconds for a network device.
> > cloud-init-nonet gave up waiting for a network device.
> > ci-info: lo: 1 127.0.0.1   255.0.0.0   .
> > ci-info: eth0  : 1 .   .   fa:16:3e:56:2c:9c
> > route_info failed
> >  * Stopping Handle applying cloud-config[74G[ OK ]
> > Waiting for network configuration...
> > Waiting up to 60 more seconds for network configuration...
> > Booting system without full network configuration…
>
>
> so no dhcp, but using tcpdump i see this output:
>
> http://pastie.org/4369949
>
> and it seems ok to me.
> What else can be?
>
> Best
> ___
> 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] [nova] VM stucks in deleting task state

[Sébastien Han]

http://www.sebastien-han.fr/blog/2012/07/10/delete-a-vm-in-an-error-state/


On Thu, Jul 12, 2012 at 8:34 PM, Tong Li  wrote:

>  Hi, Hien,
>  I had same problem. The only way that I can get rid of it is to remove
> the record for that instance from the following 3 mysql db tables in the
> following order.
>
>  security_group_instance_association
>  instance_info_caches
>  instances
>
>  hope that helps.
>
> Tong Li
> Emerging Technologies & Standards
>
> [image: Inactive hide details for Hien Phan ---07/12/2012 02:08:58
> PM---Hello list, I've just installed Openstack Essex on Ubuntu 12.04]Hien
> Phan ---07/12/2012 02:08:58 PM---Hello list, I've just installed Openstack
> Essex on Ubuntu 12.04. Everything works well
>
> From: Hien Phan 
> To: openstack@lists.launchpad.net
> Date: 07/12/2012 02:08 PM
> Subject: [Openstack] [nova] VM stucks in deleting task state
> Sent by: openstack-bounces+litong01=us.ibm@lists.launchpad.net
> --
>
>
>
> Hello list,
>
> I've just installed Openstack Essex on Ubuntu 12.04. Everything works well
> except one problem I just faced:
> When I try terminate VM in dashboard. It stuck in deleting ask for few
> hours until now. I can not connect VM. I try reboot using nova command and
> error :
>
> root@openstack-node01:~# nova reboot hien-vm02
> ERROR: Cannot 'reboot' while instance is in task_state deleting (HTTP 409)
> root@openstack-node01:~# nova reboot hien-vm01
> ERROR: Cannot 'reboot' while instance is in task_state deleting (HTTP 409)
> root@openstack-node01:~# nova list
>
> +--+---++-+
> |  ID  |Name   | Status
> |   Networks  |
>
> +--+---++-+
> | b924a325-b07f-480b-9a31-3049736fbfde | hien-vm02 | ACTIVE |
> private=172.16.1.35, 192.168.255.34 |
> | e7908096-83e6-480d-9131-efa4ea73ca0d | hien-vm01 | ACTIVE |
> private=172.16.1.34, 192.168.255.33 |
>
> +--+---++-+
>
>
>
> Openstack Dashboard screenshot image: 
> *http://i.imgur.com/7e4cf.png*
>
> How i can delete VMs completely ?
> Thanks in advance.
> --
> Best regards,
> Phan Quoc Hien
> *
> * 
> ___
> 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] Nova Scheduler issue

[Sébastien Han]

$ sudo nova-manage service disable --host=ESSEX-1 --service nova-compute

It's also good to read the documentation before asking questions.

http://docs.openstack.org/essex/openstack-compute/admin/content/managing-the-cloud.html#d6e6254

Cheers.

On Thu, Jul 12, 2012 at 9:14 AM, Christian Wittwer wrote:

> You can just stop nova-compute on the essex-1 node.
>
> 2012/7/12 Trinath Somanchi 
>
>> Hi-
>>
>> I have installed Openstack on a Machine ESSEX-1 which is the controller
>> and Nova-Compute on another machine ESSEX-2 which acts as an agent/node.
>>
>> When ever I start an new instance, the VM instance is getting created in
>> the CONTROLLER (ESSEX-1) machine not in the ESSEX-2 machine, the agent/node.
>>
>> Please kindly help me on how to restrict/instruct the controller to
>> create the VM instances only on the Agent/Nodes only.
>>
>> Thanking you for the help.
>>
>>
>> --
>> Regards,
>> --
>> Trinath Somanchi,
>> +91 9866 235 130
>>
>>
>> ___
>> 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] [OpenStack][Nova] Live Migration Error

[Sébastien Han]

Np ;)

On Tue, Jul 10, 2012 at 12:33 PM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> Ok. Thx for the help :)
>
>
> On Tue, Jul 10, 2012 at 11:30 AM, Sébastien Han 
> wrote:
>
>> It's production ready, RedHat offers a commercial support on it.
>> Just keep in mind that it's owned by Redhat ;)
>>
>>
>>
>> On Tue, Jul 10, 2012 at 12:24 PM, Leander Bessa Beernaert <
>> leande...@gmail.com> wrote:
>>
>>> Is GlusterFS be more viable for a production environment?
>>>
>>>
>>> On Tue, Jul 10, 2012 at 11:17 AM, Sébastien Han >> > wrote:
>>>
>>>> Great!
>>>>
>>>> The last time I ran the live-migration, it was with GlusterFS and
>>>> CephFS and I didn't changed any permissions in libvirt. I did the
>>>> live-migration with NFS once but it was in Diablo (horrible), I don't
>>>> really remember my setup. Maybe you should consider to try GlusterFS.
>>>>
>>>>
>>>> On Tue, Jul 10, 2012 at 12:07 PM, Leander Bessa Beernaert <
>>>> leande...@gmail.com> wrote:
>>>>
>>>>> That did! Thanks :)
>>>>>
>>>>> Do you by change have any pointer on getting the live-migration to
>>>>> work without running libvirt under root?
>>>>>
>>>>>
>>>>> On Tue, Jul 10, 2012 at 10:55 AM, Sébastien Han <
>>>>> han.sebast...@gmail.com> wrote:
>>>>>
>>>>>> Change the vncserver_listen to 0.0.0.0 and re-try the live-migration,
>>>>>> you should get better results :)
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 10, 2012 at 11:52 AM, Leander Bessa Beernaert <
>>>>>> leande...@gmail.com> wrote:
>>>>>>
>>>>>>> If i don't run libvirt with root, it can't write to the shared
>>>>>>> folder. It's the only way i've been able to get this to work. :S
>>>>>>>
>>>>>>> Below follows the configuration of one of the compute nodes.
>>>>>>> 10.0.1.1 is the controller and 10.0.1.2 is the compute node.
>>>>>>>
>>>>>>> novncproxy_base_url=http://10.0.1.1:6080/vnc_auto.html
>>>>>>>> xvpvncproxy_base_url=http://10.0.1.1:6081/console
>>>>>>>> vncserver_proxyclient_address=10.0.1.2
>>>>>>>> vncserver_listen=10.0.1.2
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jul 10, 2012 at 10:49 AM, Sébastien Han <
>>>>>>> han.sebast...@gmail.com> wrote:
>>>>>>>
>>>>>>>> I forgot to ask, did you enable the vnc console?
>>>>>>>>
>>>>>>>> If so, with which parameters?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jul 10, 2012 at 11:48 AM, Sébastien Han <
>>>>>>>> han.sebast...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi!
>>>>>>>>>
>>>>>>>>> Usually you get:
>>>>>>>>>
>>>>>>>>> 2012-07-09 13:58:27.179+: 10227: warning :
>>>>>>>>>> qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002'
>>>>>>>>>> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> when you change permission in libvirt (root I presumed) which is
>>>>>>>>> not necessary.
>>>>>>>>>
>>>>>>>>> 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 :
>>>>>>>>>> Cannot find 'pm-is-supported' in path: No such file or directory
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> This error is harmless and can be easily solved by installing the
>>>>>>>>> following package:
>>>>>>>>>
>>>>>>>>> sudo apt-get install pm-utils -y
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Do you have something in the nova-scheduler logs?
>>>>>>>>>
>>>>>>&

Re: [Openstack] [OpenStack][Nova] Live Migration Error

[Sébastien Han]

It's production ready, RedHat offers a commercial support on it.
Just keep in mind that it's owned by Redhat ;)


On Tue, Jul 10, 2012 at 12:24 PM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> Is GlusterFS be more viable for a production environment?
>
>
> On Tue, Jul 10, 2012 at 11:17 AM, Sébastien Han 
> wrote:
>
>> Great!
>>
>> The last time I ran the live-migration, it was with GlusterFS and CephFS
>> and I didn't changed any permissions in libvirt. I did the live-migration
>> with NFS once but it was in Diablo (horrible), I don't really remember my
>> setup. Maybe you should consider to try GlusterFS.
>>
>>
>> On Tue, Jul 10, 2012 at 12:07 PM, Leander Bessa Beernaert <
>> leande...@gmail.com> wrote:
>>
>>> That did! Thanks :)
>>>
>>> Do you by change have any pointer on getting the live-migration to work
>>> without running libvirt under root?
>>>
>>>
>>> On Tue, Jul 10, 2012 at 10:55 AM, Sébastien Han >> > wrote:
>>>
>>>> Change the vncserver_listen to 0.0.0.0 and re-try the live-migration,
>>>> you should get better results :)
>>>>
>>>>
>>>>
>>>> On Tue, Jul 10, 2012 at 11:52 AM, Leander Bessa Beernaert <
>>>> leande...@gmail.com> wrote:
>>>>
>>>>> If i don't run libvirt with root, it can't write to the shared folder.
>>>>> It's the only way i've been able to get this to work. :S
>>>>>
>>>>> Below follows the configuration of one of the compute nodes. 10.0.1.1
>>>>> is the controller and 10.0.1.2 is the compute node.
>>>>>
>>>>> novncproxy_base_url=http://10.0.1.1:6080/vnc_auto.html
>>>>>> xvpvncproxy_base_url=http://10.0.1.1:6081/console
>>>>>> vncserver_proxyclient_address=10.0.1.2
>>>>>> vncserver_listen=10.0.1.2
>>>>>
>>>>>
>>>>> On Tue, Jul 10, 2012 at 10:49 AM, Sébastien Han <
>>>>> han.sebast...@gmail.com> wrote:
>>>>>
>>>>>> I forgot to ask, did you enable the vnc console?
>>>>>>
>>>>>> If so, with which parameters?
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 10, 2012 at 11:48 AM, Sébastien Han <
>>>>>> han.sebast...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi!
>>>>>>>
>>>>>>> Usually you get:
>>>>>>>
>>>>>>> 2012-07-09 13:58:27.179+: 10227: warning :
>>>>>>>> qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002'
>>>>>>>> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
>>>>>>>
>>>>>>>
>>>>>>> when you change permission in libvirt (root I presumed) which is not
>>>>>>> necessary.
>>>>>>>
>>>>>>> 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 :
>>>>>>>> Cannot find 'pm-is-supported' in path: No such file or directory
>>>>>>>
>>>>>>>
>>>>>>> This error is harmless and can be easily solved by installing the
>>>>>>> following package:
>>>>>>>
>>>>>>> sudo apt-get install pm-utils -y
>>>>>>>
>>>>>>>
>>>>>>> Do you have something in the nova-scheduler logs?
>>>>>>>
>>>>>>> Cheers!
>>>>>>>
>>>>>>> On Tue, Jul 10, 2012 at 11:29 AM, Leander Bessa Beernaert <
>>>>>>> leande...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Well i've checked the libvirt logs on both nodes and i found these
>>>>>>>> two lines:
>>>>>>>>
>>>>>>>> 2012-07-09 13:58:27.179+: 10227: warning :
>>>>>>>>> qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002'
>>>>>>>>> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
>>>>>>>>> 2012-07-09 13:58:27.736+: 10226: error : qemuMonitorIORead:513
>>>>>>>>> : Unable to read from monitor: Connection reset by peer
>>>>>>>>
>>>>&g

Re: [Openstack] [OpenStack][Nova] Live Migration Error

[Sébastien Han]

Great!

The last time I ran the live-migration, it was with GlusterFS and CephFS
and I didn't changed any permissions in libvirt. I did the live-migration
with NFS once but it was in Diablo (horrible), I don't really remember my
setup. Maybe you should consider to try GlusterFS.


On Tue, Jul 10, 2012 at 12:07 PM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> That did! Thanks :)
>
> Do you by change have any pointer on getting the live-migration to work
> without running libvirt under root?
>
>
> On Tue, Jul 10, 2012 at 10:55 AM, Sébastien Han 
> wrote:
>
>> Change the vncserver_listen to 0.0.0.0 and re-try the live-migration, you
>> should get better results :)
>>
>>
>>
>> On Tue, Jul 10, 2012 at 11:52 AM, Leander Bessa Beernaert <
>> leande...@gmail.com> wrote:
>>
>>> If i don't run libvirt with root, it can't write to the shared folder.
>>> It's the only way i've been able to get this to work. :S
>>>
>>> Below follows the configuration of one of the compute nodes. 10.0.1.1 is
>>> the controller and 10.0.1.2 is the compute node.
>>>
>>> novncproxy_base_url=http://10.0.1.1:6080/vnc_auto.html
>>>> xvpvncproxy_base_url=http://10.0.1.1:6081/console
>>>> vncserver_proxyclient_address=10.0.1.2
>>>> vncserver_listen=10.0.1.2
>>>
>>>
>>> On Tue, Jul 10, 2012 at 10:49 AM, Sébastien Han >> > wrote:
>>>
>>>> I forgot to ask, did you enable the vnc console?
>>>>
>>>> If so, with which parameters?
>>>>
>>>>
>>>> On Tue, Jul 10, 2012 at 11:48 AM, Sébastien Han <
>>>> han.sebast...@gmail.com> wrote:
>>>>
>>>>> Hi!
>>>>>
>>>>> Usually you get:
>>>>>
>>>>> 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134
>>>>>> : Domain id=2 name='instance-0002'
>>>>>> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
>>>>>
>>>>>
>>>>> when you change permission in libvirt (root I presumed) which is not
>>>>> necessary.
>>>>>
>>>>> 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 :
>>>>>> Cannot find 'pm-is-supported' in path: No such file or directory
>>>>>
>>>>>
>>>>> This error is harmless and can be easily solved by installing the
>>>>> following package:
>>>>>
>>>>> sudo apt-get install pm-utils -y
>>>>>
>>>>>
>>>>> Do you have something in the nova-scheduler logs?
>>>>>
>>>>> Cheers!
>>>>>
>>>>> On Tue, Jul 10, 2012 at 11:29 AM, Leander Bessa Beernaert <
>>>>> leande...@gmail.com> wrote:
>>>>>
>>>>>> Well i've checked the libvirt logs on both nodes and i found these
>>>>>> two lines:
>>>>>>
>>>>>> 2012-07-09 13:58:27.179+: 10227: warning :
>>>>>>> qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002'
>>>>>>> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
>>>>>>> 2012-07-09 13:58:27.736+: 10226: error : qemuMonitorIORead:513 :
>>>>>>> Unable to read from monitor: Connection reset by peer
>>>>>>
>>>>>>
>>>>>> The log is alos filled with the message below, it gets repeated over
>>>>>> and over and over.
>>>>>>
>>>>>> 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 :
>>>>>>> Cannot find 'pm-is-supported' in path: No such file or directory
>>>>>>> 2012-07-10 09:26:02.244+: 10229: warning : qemuCapsInit:856 :
>>>>>>> Failed to get host power management capabilities
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 10, 2012 at 8:16 AM, Razique Mahroua <
>>>>>> razique.mahr...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Leander,
>>>>>>> try to check libvirtd.log files,
>>>>>>> is the instance still running on the first node while you are
>>>>>>> lauching the migration process ?
>>>>>>>
>>>>>>> Razique
>>>>>>>  *Nuage & Co - 

Re: [Openstack] [OpenStack][Nova] Live Migration Error

[Sébastien Han]

Change the vncserver_listen to 0.0.0.0 and re-try the live-migration, you
should get better results :)


On Tue, Jul 10, 2012 at 11:52 AM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> If i don't run libvirt with root, it can't write to the shared folder.
> It's the only way i've been able to get this to work. :S
>
> Below follows the configuration of one of the compute nodes. 10.0.1.1 is
> the controller and 10.0.1.2 is the compute node.
>
> novncproxy_base_url=http://10.0.1.1:6080/vnc_auto.html
>> xvpvncproxy_base_url=http://10.0.1.1:6081/console
>> vncserver_proxyclient_address=10.0.1.2
>> vncserver_listen=10.0.1.2
>
>
> On Tue, Jul 10, 2012 at 10:49 AM, Sébastien Han 
> wrote:
>
>> I forgot to ask, did you enable the vnc console?
>>
>> If so, with which parameters?
>>
>>
>> On Tue, Jul 10, 2012 at 11:48 AM, Sébastien Han 
>> wrote:
>>
>>> Hi!
>>>
>>> Usually you get:
>>>
>>> 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 :
>>>> Domain id=2 name='instance-0002'
>>>> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
>>>
>>>
>>> when you change permission in libvirt (root I presumed) which is not
>>> necessary.
>>>
>>> 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 :
>>>> Cannot find 'pm-is-supported' in path: No such file or directory
>>>
>>>
>>> This error is harmless and can be easily solved by installing the
>>> following package:
>>>
>>> sudo apt-get install pm-utils -y
>>>
>>>
>>> Do you have something in the nova-scheduler logs?
>>>
>>> Cheers!
>>>
>>> On Tue, Jul 10, 2012 at 11:29 AM, Leander Bessa Beernaert <
>>> leande...@gmail.com> wrote:
>>>
>>>> Well i've checked the libvirt logs on both nodes and i found these two
>>>> lines:
>>>>
>>>> 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134
>>>>> : Domain id=2 name='instance-0002'
>>>>> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
>>>>> 2012-07-09 13:58:27.736+: 10226: error : qemuMonitorIORead:513 :
>>>>> Unable to read from monitor: Connection reset by peer
>>>>
>>>>
>>>> The log is alos filled with the message below, it gets repeated over
>>>> and over and over.
>>>>
>>>> 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 :
>>>>> Cannot find 'pm-is-supported' in path: No such file or directory
>>>>> 2012-07-10 09:26:02.244+: 10229: warning : qemuCapsInit:856 :
>>>>> Failed to get host power management capabilities
>>>>
>>>>
>>>> On Tue, Jul 10, 2012 at 8:16 AM, Razique Mahroua <
>>>> razique.mahr...@gmail.com> wrote:
>>>>
>>>>> Hi Leander,
>>>>> try to check libvirtd.log files,
>>>>> is the instance still running on the first node while you are lauching
>>>>> the migration process ?
>>>>>
>>>>> Razique
>>>>>  *Nuage & Co - Razique Mahroua** *
>>>>> razique.mahr...@gmail.com
>>>>>
>>>>>
>>>>> Le 9 juil. 2012 à 16:09, Leander Bessa Beernaert a écrit :
>>>>>
>>>>> Ok, so i've updated to the test packages from
>>>>>
>>>>> The migration still fails, but i see no errors in the logs. I'm trying
>>>>> to migrate a VM with the m1.tiny flavor from one machine to another. Their
>>>>> hardware are identical and they have more than enough resources to support
>>>>> the m1.tiny flavor:
>>>>>
>>>>> cloud35 (total) 43867 186
>>>>>> cloud35 (used_now)  0 312   5
>>>>>> cloud35 (used_max)  0   0   0
>>>>>
>>>>>
>>>>> These are the logs from the origin compute node:
>>>>> http://paste.openstack.org/show/19319/  and  the destination compute
>>>>> node: http://paste.openstack.org/show/19318/ . The scheduler's log
>>>>> has no visible errors or stack traces.
>>>>>
>>>>> I'm still using nfsv4.
>>>>>

Re: [Openstack] [OpenStack][Nova] Live Migration Error

[Sébastien Han]

I forgot to ask, did you enable the vnc console?

If so, with which parameters?


On Tue, Jul 10, 2012 at 11:48 AM, Sébastien Han wrote:

> Hi!
>
> Usually you get:
>
> 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 :
>> Domain id=2 name='instance-0002'
>> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
>
>
> when you change permission in libvirt (root I presumed) which is not
> necessary.
>
> 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot
>> find 'pm-is-supported' in path: No such file or directory
>
>
> This error is harmless and can be easily solved by installing the
> following package:
>
> sudo apt-get install pm-utils -y
>
>
> Do you have something in the nova-scheduler logs?
>
> Cheers!
>
> On Tue, Jul 10, 2012 at 11:29 AM, Leander Bessa Beernaert <
> leande...@gmail.com> wrote:
>
>> Well i've checked the libvirt logs on both nodes and i found these two
>> lines:
>>
>> 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 :
>>> Domain id=2 name='instance-0002'
>>> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
>>> 2012-07-09 13:58:27.736+: 10226: error : qemuMonitorIORead:513 :
>>> Unable to read from monitor: Connection reset by peer
>>
>>
>> The log is alos filled with the message below, it gets repeated over and
>> over and over.
>>
>> 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot
>>> find 'pm-is-supported' in path: No such file or directory
>>> 2012-07-10 09:26:02.244+: 10229: warning : qemuCapsInit:856 : Failed
>>> to get host power management capabilities
>>
>>
>> On Tue, Jul 10, 2012 at 8:16 AM, Razique Mahroua <
>> razique.mahr...@gmail.com> wrote:
>>
>>> Hi Leander,
>>> try to check libvirtd.log files,
>>> is the instance still running on the first node while you are lauching
>>> the migration process ?
>>>
>>> Razique
>>>  *Nuage & Co - Razique Mahroua** *
>>> razique.mahr...@gmail.com
>>>
>>>
>>> Le 9 juil. 2012 à 16:09, Leander Bessa Beernaert a écrit :
>>>
>>> Ok, so i've updated to the test packages from
>>>
>>> The migration still fails, but i see no errors in the logs. I'm trying
>>> to migrate a VM with the m1.tiny flavor from one machine to another. Their
>>> hardware are identical and they have more than enough resources to support
>>> the m1.tiny flavor:
>>>
>>> cloud35 (total) 43867 186
>>>> cloud35 (used_now)  0 312   5
>>>> cloud35 (used_max)  0   0   0
>>>
>>>
>>> These are the logs from the origin compute node:
>>> http://paste.openstack.org/show/19319/  and  the destination compute
>>> node: http://paste.openstack.org/show/19318/ . The scheduler's log has
>>> no visible errors or stack traces.
>>>
>>> I'm still using nfsv4.
>>>
>>> Any ideas?
>>>
>>>
>>> On Fri, Jul 6, 2012 at 7:57 PM, Leander Bessa Beernaert <
>>> leande...@gmail.com> wrote:
>>>
>>>> Thanks for the tip, it's a better than nothing :)
>>>>
>>>> Regards,
>>>> Leander
>>>>
>>>> On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे <
>>>> mandarv...@gmail.com> wrote:
>>>>
>>>>> Not sure if you are able to debug this, but a while ago there was a
>>>>> bug where instance.id was passed where instance.uuid was expected.
>>>>> This used to cause some problem.
>>>>> It looks like you are using distribution package rather than devstack
>>>>> installation, so it is likely that the issue is now fixed. Can you try
>>>>> latest packages (and/or try devstack if you can)
>>>>>
>>>>> I wish I could help more.
>>>>>
>>>>> -Mandar
>>>>>
>>>>>
>>>>> On Fri, Jul 6, 2012 at 3:26 PM, Leander Bessa Beernaert <
>>>>> leande...@gmail.com> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I've recently setup a system to test out the live migration feature.
>>>>>> So far i've been able to launch th

Re: [Openstack] [OpenStack][Nova] Live Migration Error

[Sébastien Han]

Hi!

Usually you get:

2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 :
> Domain id=2 name='instance-0002'
> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges


when you change permission in libvirt (root I presumed) which is not
necessary.

2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot
> find 'pm-is-supported' in path: No such file or directory


This error is harmless and can be easily solved by installing the following
package:

sudo apt-get install pm-utils -y


Do you have something in the nova-scheduler logs?

Cheers!

On Tue, Jul 10, 2012 at 11:29 AM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> Well i've checked the libvirt logs on both nodes and i found these two
> lines:
>
> 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 :
>> Domain id=2 name='instance-0002'
>> uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
>> 2012-07-09 13:58:27.736+: 10226: error : qemuMonitorIORead:513 :
>> Unable to read from monitor: Connection reset by peer
>
>
> The log is alos filled with the message below, it gets repeated over and
> over and over.
>
> 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot
>> find 'pm-is-supported' in path: No such file or directory
>> 2012-07-10 09:26:02.244+: 10229: warning : qemuCapsInit:856 : Failed
>> to get host power management capabilities
>
>
> On Tue, Jul 10, 2012 at 8:16 AM, Razique Mahroua <
> razique.mahr...@gmail.com> wrote:
>
>> Hi Leander,
>> try to check libvirtd.log files,
>> is the instance still running on the first node while you are lauching
>> the migration process ?
>>
>> Razique
>>  *Nuage & Co - Razique Mahroua** *
>> razique.mahr...@gmail.com
>>
>>
>> Le 9 juil. 2012 à 16:09, Leander Bessa Beernaert a écrit :
>>
>> Ok, so i've updated to the test packages from
>>
>> The migration still fails, but i see no errors in the logs. I'm trying to
>> migrate a VM with the m1.tiny flavor from one machine to another. Their
>> hardware are identical and they have more than enough resources to support
>> the m1.tiny flavor:
>>
>> cloud35 (total) 43867 186
>>> cloud35 (used_now)  0 312   5
>>> cloud35 (used_max)  0   0   0
>>
>>
>> These are the logs from the origin compute node:
>> http://paste.openstack.org/show/19319/  and  the destination compute
>> node: http://paste.openstack.org/show/19318/ . The scheduler's log has
>> no visible errors or stack traces.
>>
>> I'm still using nfsv4.
>>
>> Any ideas?
>>
>>
>> On Fri, Jul 6, 2012 at 7:57 PM, Leander Bessa Beernaert <
>> leande...@gmail.com> wrote:
>>
>>> Thanks for the tip, it's a better than nothing :)
>>>
>>> Regards,
>>> Leander
>>>
>>> On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे <
>>> mandarv...@gmail.com> wrote:
>>>
 Not sure if you are able to debug this, but a while ago there was a bug
 where instance.id was passed where instance.uuid was expected. This
 used to cause some problem.
 It looks like you are using distribution package rather than devstack
 installation, so it is likely that the issue is now fixed. Can you try
 latest packages (and/or try devstack if you can)

 I wish I could help more.

 -Mandar


 On Fri, Jul 6, 2012 at 3:26 PM, Leander Bessa Beernaert <
 leande...@gmail.com> wrote:

> Hello,
>
> I've recently setup a system to test out the live migration feature.
> So far i've been able to launch the instances with the shared nfs folder.
> However, when i run the live-migration command i encounter this error in
> the destination compute node:
>
> 2012-07-05 09:33:48 ERROR nova.manager [-] Error during
>> ComputeManager.update_available_resource: Domain not found: no domain 
>> with
>> matching id 2
>> 2012-07-05 09:33:48 TRACE nova.manager Traceback (most recent call
>> last):
>> 2012-07-05 09:33:48 TRACE nova.manager   File
>> "/usr/lib/python2.7/dist-packages/nova/manager.py", line 155, in
>> periodic_tasks
>> 2012-07-05 09:33:48 TRACE nova.manager task(self, context)
>> 2012-07-05 09:33:48 TRACE nova.manager   File
>> "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2409, in
>> update_available_resource
>> 2012-07-05 09:33:48 TRACE nova.manager
>> self.driver.update_available_resource(context, self.host)
>> 2012-07-05 09:33:48 TRACE nova.manager   File
>> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line
>> 1936, in update_available_resource
>> 2012-07-05 09:33:48 TRACE nova.manager 'vcpus_used':
>> self.get_vcpu_used(),
>> 2012-07-05 09:33:48 TRACE nova.manager   File
>> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line
>> 1743, in get_vcpu_used
>> 2012-07-05 09

Re: [Openstack] Nova Pacemaker Resource Agents

[Sébastien Han]

Ok thanks! I will have a look :D

We keep in touch ;)


On Tue, Jul 3, 2012 at 4:09 PM, Christian Parpart  wrote:

> On Tue, Jul 3, 2012 at 1:35 PM, Sébastien Han wrote:
>
>> Hi,
>>
>> Managing a resource via LSB only checks the PID. If the PID exists the
>> service is running but it's not enough because it doesn't mean that the
>> service is truly functionnal. However OCF agents offer more features like
>> fine monitoring (scripting).
>> I'm not sure to understand your question about Rabbit-MQ but if the
>> question was: "How do you monitor the connection of each service to
>> Rabbit-MQ?", here is the answer:
>>
>> The RA monitors the connection state (ESTABLISHED) between the service
>> (nova-scheduler, nova-cert, nova-consoleauth) and rabbit-MQ according to
>> the PID of the process.
>>
>> By the way, did you start with the floating IP OCF agent?
>>
>
> Hey,
>
> and yes, I did start already, and have an intial work of it, but since I
> did not
> yet actually put it into Pacemaker somewhere, I did not share it yet.
> But you may feel free in checking: http://trapni.de/~trapni/FloatingIP
> In case you do improvements to this script, please share :-)
>
> Cheers,
> Christian.
>
___
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] [OpenStack][Nova] Live Migration + NFSv4 - Permission issues

[Sébastien Han]

Which permissions did you set on /var/lib/nova/instances?


On Tue, Jul 3, 2012 at 3:48 PM, Leander Bessa Beernaert  wrote:

> Hello all,
>
> I've been trying to get the live migration to work according to the guide
> http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html.
>
> So far i've setup 2 compute nodes and 1 controller node. They all share
> the /var/lib/nova/instances dir. I've already verified that the nova user
> id is the same across all the servers.
>
> Currently i'm running into this error when i launch an instance:
> http://paste.openstack.org/show/19221/
>
> It's certainly a permission issue, so i tried adding the group "nova" to
> the user "libvirt-qemu". However, it still doesn't work. To which user must
> i give the nova group permission in order to be able to write in that
> directory?
>
> Regards,
> Leander
>
> ___
> 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] Nova Pacemaker Resource Agents

[Sébastien Han]

Hi,

Managing a resource via LSB only checks the PID. If the PID exists the
service is running but it's not enough because it doesn't mean that the
service is truly functionnal. However OCF agents offer more features like
fine monitoring (scripting).
I'm not sure to understand your question about Rabbit-MQ but if the
question was: "How do you monitor the connection of each service to
Rabbit-MQ?", here is the answer:

The RA monitors the connection state (ESTABLISHED) between the service
(nova-scheduler, nova-cert, nova-consoleauth) and rabbit-MQ according to
the PID of the process.

By the way, did you start with the floating IP OCF agent?

Cheers.


On Tue, Jul 3, 2012 at 12:45 PM, Christian Parpart  wrote:

> Hey,
>
> that's great, but how do you handle RabbitMQ in-between?
>
> I kind of achieved it w/o OCF agents but used native upstart support of
> Pacemaker, however,
> OCF's are much more nicer, and still, I'd be interested in how you solved
> the RabbitMQ issue.
>
> Best regards,
> Christian Parpart.
>
> On Mon, Jul 2, 2012 at 7:38 PM, Sébastien Han wrote:
>
>> Hi everyone,
>>
>> For those of you who want to achieve HA in nova. I wrote some resource
>> agents according to the OCF specification. The RAs available are:
>>
>>- nova-scheduler
>>- nova-api
>>- novnc
>>- nova-consoleauth
>>- nova-cert
>>
>> The how-to is available here:
>> http://www.sebastien-han.fr/blog/2012/07/02/openstack-nova-components-ha/ and
>> the RAs on my Github https://github.com/leseb/OpenStack-ra
>>
>> Those RAs mainly re-use the structure of the resource agent written by
>> Martin Gerhard Loschwitz from Hastexo.
>>
>> Hope it helps!
>>
>> Cheers.
>>
>> ~Seb
>>
>>
>> ___
>> 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] Nova Pacemaker Resource Agents

[Sébastien Han]

Hi everyone,

For those of you who want to achieve HA in nova. I wrote some resource
agents according to the OCF specification. The RAs available are:

   - nova-scheduler
   - nova-api
   - novnc
   - nova-consoleauth
   - nova-cert

The how-to is available here:
http://www.sebastien-han.fr/blog/2012/07/02/openstack-nova-components-ha/ and
the RAs on my Github https://github.com/leseb/OpenStack-ra

Those RAs mainly re-use the structure of the resource agent written by
Martin Gerhard Loschwitz from Hastexo.

Hope it helps!

Cheers.

~Seb
___
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] storage backend for nova

[Sébastien Han]

Hi,

I'm sure if I understand everything but let me give a try.
By default, the compute nodes store virtual instances in
/var/lib/nova/instances/. Of course it's part of the compute node local FS.
If you want to store this directory somewhere else, use a DFS like
GlusterFS or even Ceph or a SAN.
Also don't forget that you *can't *use Swift for storing your virtual
instances.

Hope it is what you asked for.

Cheers.

On Thu, Jun 28, 2012 at 1:48 AM, udit agarwal  wrote:

> Hi,
>  I have set up Openstack in my lab with everything except storage nodes on
> one system and two other systems with each of them acting themselves as a
> storage node. I have used swift as the backend for glance so all the
> uploaded images are stored on these storage nodes. But when I run a virtual
> machine using nova, it reads the image from the storage nodes and it seems
> to me that it uses the local filesystem for storing instances and after I
> shutoff my virtual machine, it writes back to the storage nodes. But the
> thing that I want to implement is that if I copy some file from my local
> system to that virtual machine, it should automatically get stored on my
> storage nodes rather than occupying space on my local filesystem.
>
>  Can anybody help me with this??
>  Thanks in advance.
>
> --Udit Agarwal
>
> ___
> 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] How to use Cloudpipe

[Sébastien Han]

Hi,

The official doc needs to be updated at some points. If you want to make
this compatible with Ubuntu 12.04.
You can check my article here
http://www.sebastien-han.fr/blog/2012/06/20/setup-cloud-pipe-vpn-in-openstack/and
the fork of the mirantis repo
https://github.com/leseb/cloudpipe-image-auto-creation/blob/master/cloudpipeconf.sh

I will also try to  update the OpenStacj wiki asap.

Cheers.


On Thu, Jun 21, 2012 at 7:01 AM, Atul Jha  wrote:

> Hi Naveen,
> 
> From: 
> openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha=
> csscorp@lists.launchpad.net] on behalf of Naveen Kuna [
> naveen.k...@oneconvergence.com]
> Sent: Thursday, June 21, 2012 8:22 AM
> To: openstack@lists.launchpad.net
> Subject: [Openstack] How to use Cloudpipe
>
> Hi All,
>
> Can anyone help me in making cloudpipe image and how to use cloudpipe
> image for VPN service ?
>
>
> http://docs.openstack.org/trunk/openstack-compute/admin/content/cloudpipe-per-project-vpns.html
>
> Please go through documentation pages next time onwards before asking
> questions which are already easily available.
>
> Thanks in Advance
>
> Regards,
> Naveen
>
> Cheers!!
>
> Atul
> http://www.csscorp.com/common/email-disclaimer.php
>
> ___
> 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] Multiple nova-compute hosts, single-host nova-network, and a guest unreachable via its floating IP

[Sébastien Han]

Hi Florian,

For my own setup, I wanted to achieve highly-available network, and avoid
the loss of the gateway of every instances running if nova-network falls
down. I couldn't afford 2 dedicated nodes to put nova-network itself in an
highly available state. Now if I loose a nova-network on a compute node,
all my instances running on this compute node will loose their gateway but
this scenario is better than loosing all my VMs. The multi_host was the
best option and I think it's applicable to every setup. So precisely, every
compute node hosts those services:

   - nova-compute
   - nova-network - avoid networking SPOF
   - nova-api-metadata - you don't need the entire nova-api service. Each
   new instance only needs to reach the metadata. Running this from the
   compute node can also improve performance with the cloud-init service.

Of course this setup works with the multi_host parameter enable.

My 2 cts contribution ;)

On Tue, Jun 19, 2012 at 7:52 PM, Florian Haas  wrote:
> Hi everyone,
>
> perhaps someone can shed some light on a floating IP issue.
>
> I have 2 nova-compute nodes (call them alice and bob), one of them
> (alice) is also running nova-network. bob uses alice as its
> --metadata_host and --network_host.
>
> I assign a floating IP to a guest running on bob. Expectedly, that IP
> is bound to the NIC specified as the --public_interface on alice (my
> nova-network host).
>
> However, since alice has a route into the --fixed_range network over
> its local bridge, the incoming traffic for the floating IP is routed
> there, where there's no guest to answer it -- because the guest is,
> after all, running on bob.
>
> Now, this seems fairly logical to me in the combination of
>
> 1. a nova-network host also running nova-compute;
> 2. other nova-compute hosts being around;
> 3. those other nova-compute hosts _not_ also running nova-network (and
> hence there being no multi-host networking).
>
> If my reasoning is correct, is it safe to say that in order to be able
> to use floating IPs in an environment with multiple nova-compute
> hosts, you must
>
> 1. Either have a single nova-network host that is _not_ also running
> nova-compute (but has a network connection to the --fixed_range
> network, of course);
> 2. or run nova-network on all your nova-compute hosts, which however
> requires that you enable multi-host mode and also run nova-api there?
>
> Any help is much appreciated. Thanks!
>
> Cheers,
> Florian
>
> ___
> 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] storage for virtual machines

[Sébastien Han]

Hi,

If you planned to use Swift to store the virtual images disk and run
instance over Swift: it's not possible.
If you planned to use swift for nova-volume (cinder) and attaching disk:
it's also not possible.

Swift is *NOT*:

   - a filesystem
   - a block device

Perhaps, Swift can be use as a backend for Glance and of course object
storage like S3.

Someone correct me if I'm wrong.

Cheers.


On Tue, Jun 12, 2012 at 12:39 PM, Udit Agarwal  wrote:

> Hi,
>
>   I have setup nova compute and storage on different nodes. I want to
> create new virtual machine images on my nova compute node. I also want to
> configure these virtual machines to use swift(openstack storage that is
> setup on a different node) for their storage purposes. But I have no idea
> how to do this? Can anyone help me in this matter.
>
> ** **
>
>   Thanks in advance.
>
> 
>
> ** **
>
> --Udit Agarwal 
>
> ___
> 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] Ceph + OpenStack [HOW-TO]

[Sébastien Han]

Hello everyone,

I recently posted on my website an introduction to ceph and the integration
of Ceph in OpenStack.
It could be really helpful since the OpenStack documentation has not dealt
with it so far.

Feel free to comment, express your opinions and share your personal
experience about both of them.

Here the link to the article:
http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/

Regards.

Sébastien Han.
___
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] [SOLVED] Re: "nova live-migration" failing on Ubuntu precise; libvirt live migration is OK

[Sébastien Han]

Hello,

I'm not affected by this issue. I was, but it was related to the vnc issue,
after disabling the console, the live-migration is performed without any
problems.

Regards.

On Sat, Jun 9, 2012 at 8:59 PM, Anne Gentle
wrote:

> Absolutely should be mentioned in the docs - thanks for uncovering!
>
> Anne Gentle
> Content Stacker
> a...@openstack.org
>
>
> On Jun 9, 2012, at 1:49 PM, Florian Haas  wrote:
>
> > On 06/07/12 14:21, Florian Haas wrote:
> >> On Thu, Jun 7, 2012 at 9:53 AM, Thierry Carrez 
> wrote:
> >>> Florian Haas wrote:
>  a few people have reported issues with live migration lately, and
>  I've been digging into them to narrow them down.
> 
>  The symptom is relatively easy to describe: you run "nova
> live-migration
>   ", and nothing happens.
>  [...]
>  I'd be thankful for any clues as to where to dig further.
> >>>
> >>> You should submit a bug on the bugtracker about that, and continue the
> >>> discussion there (pointing to the bug number from here)... I'd hate to
> >>> see this one fall under the radar because it's not properly tracked.
> >>
> >> Done: https://bugs.launchpad.net/nova/+bug/1009974
> >
> > Apologies for the noise. I had mistakenly believed that since the list
> > of --live_migration_flags contained spaces, it was OK to quote the
> > --live_migration_* options. Evidently it's not, as removing the double
> > quotes made the problem go away. My guests now do migrate.
> >
> > Anne/Thierry: I've thus far been unable to find any documentation that
> > says "don't use double quotes in nova.conf". In fact,
> >
> http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html
> > uses them in several places, including the --live_migration* flags. That
> > quotes can break things appears to be a known issue as per
> > https://bugs.launchpad.net/nova/+bug/987473. Is this something that we
> > should mention in the documentation, or is this unexpected parser
> > behavior that needs to get fixed?
> >
> > Cheers,
> > Florian
> >
>
> ___
> 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] After nova-network setup, I loose Internet access

[Sébastien Han]

Hi,

Which tests did you perform in order to recover your internet connectivity?
It might seem stupid but did you check your /etc/resolv.conf, try to
desinstall/reinstall nova-network, flush the iptables?

Tell us more about the recovery tests you've already done, after this we
will be able go further :)

Cheers!


On Wed, May 30, 2012 at 2:03 PM, Emilien Macchi  wrote:

> Hi Stackers,
>
>
> I'm working on a multi-node architecture with Ubuntu 12.04 / Openstack
> Essex from Ubuntu packages :
>
> 1 controller (with Rabbit-MQ, MySQL, Nova-API, Nova-Schedule), 1 network
> (nova-network), 1 compute (nova-compute with KVM).
>
> When I setup a fresh nova-network node, I do (and nothing else after
> upgrade) :
>
> *apt-get install nova-network*
>
> After this command, I loose Internet access, but can reach the server from
> my LAN.
>
> Here you can find my 
> iptables-saveresult.
>
> My routing table :
>
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> *default 10.15.100.4 0.0.0.0 UG10000
> eth0*
> 10.15.0.0   *   255.255.0.0 U 0  00
> eth0
>
>
> Where *10.15.100.4* is my gateway.
>
>
> Any idea ?
>
>
> Regards
>
> --
> Emilien Macchi
> *SysAdmin (Intern)*
> *www.stackops.com* | emilien.mac...@stackops.com** | skype:memilien69
> *
>
> *
>
>  ADVERTENCIA LEGAL 
> Le informamos, como destinatario de este mensaje, que el correo
> electrónico y las comunicaciones por medio de Internet no permiten asegurar
> ni garantizar la confidencialidad de los mensajes transmitidos, así como
> tampoco su integridad o su correcta recepción, por lo que STACKOPS
> TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
> Si no consintiese en la utilización del correo electrónico o de las
> comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
> conocimiento de manera inmediata. Este mensaje va dirigido, de manera
> exclusiva, a su destinatario y contiene información confidencial y sujeta
> al secreto profesional, cuya divulgación no está permitida por la ley. En
> caso de haber recibido este mensaje por error, le rogamos que, de forma
> inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
> atención y proceda a su eliminación, así como a la de cualquier documento
> adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
> utilización de este mensaje, o de cualquier documento adjunto al mismo,
> cualquiera que fuera su finalidad, están prohibidas por la ley.
>
> * PRIVILEGED AND CONFIDENTIAL 
> We hereby inform you, as addressee of this message, that e-mail and
> Internet do not guarantee the confidentiality, nor the completeness or
> proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
> does not assume any liability for those circumstances. Should you not agree
> to the use of e-mail or to communications via Internet, you are kindly
> requested to notify us immediately. This message is intended exclusively
> for the person to whom it is addressed and contains privileged and
> confidential information protected from disclosure by law. If you are not
> the addressee indicated in this message, you should immediately delete it
> and any attachments and notify the sender by reply e-mail. In such case,
> you are hereby notified that any dissemination, distribution, copying or
> use of this message or any attachments, for any purpose, is strictly
> prohibited by law.
>
>
> ___
> 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] [Nova] Live migration libvirt authentication error.

[Sébastien Han]

Hi,

You forgot to add the option:

auth_tcp = "none"

after the 'listen_tls = 0' to the /etc/libvirt/libvirtd.conf file

Cheers!


On Tue, May 8, 2012 at 8:37 PM, Vishvananda Ishaya wrote:

> I haven't tried sasl so hopefully someone else has an idea.  I have
> sucessfully used qemu+ssh with ssh keys setup though.
>
> Vish
>
> On May 8, 2012, at 1:13 AM, Szymon Grzybowski wrote:
>
> Hey,
>
> I'm trying to migrate machine from HostA to HostB, but I have "
> virtNetSASLSessionClientStart:484: authentication failed:  Failed to start
> SASL negotiation: -20" in /var/log/libvirt.log when i'm trying to
> "nova live-migration  HostB"
>
> I have SASL enabled on both machines. I've tried manually connect to
> remote libvirt through virsh and defined user (ex. "virsh --connect
> qemu+tcp://HostA/system list") and everything works fine, but i have to
> give proper credentials (username/password). I saw that nova's connection
> string is also "qemu+tcp://HostA/system", but i can't see any user there.
> How does it work in nova and how can I fix it?
>
> Cheers,
>
> --
> *Semy*
>
>
> ___
> 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] rabbit MQ and mirrored queues

[Sébastien Han]

Eric,
I saw your presentation couple of weeks ago about ZeroMQ but I didn't have
time to dive into it.

In my previous statement, there is no prejudice, I simply offered an
alternative solution. I'm for the KISS principle, and using the
pacemaker/corosync/drbd stack could be a pain in the neck compared to this
easy solution provided by RabbitMQ. I also think that's highly depend on
your infrastructure, in my case I don't have thousand of nodes or geo-zones
so using 2 servers with the RabbitMQ built in cluster solution is a good
choice.
Moreover the RabbitMQ built in cluster is highly scalable and it's really
easy to add a new node.

I'm open-minded and all for new ideas.

Regards.
~Seb.

On Sat, May 26, 2012 at 12:02 AM, Eric Windisch wrote:

>  Sebastien,
>
> For my part, I don't do *any of it*. I'm the author of the ZeroMQ
> implementation, where this is a non-issue.
>
> I think that having the Rabbit queues decoupled makes a lot of sense,
> especially since the code to do this can be generalized across multiple RPC
> implementations. (i.e. this would be a win for Qpid as well)   I'm clearly
> not a die-hard RabbitMQ admin -- is there a reason to use clustering over a
> decoupled solution for a greenfield application?
>
> --
> Eric Windisch
>
> On Friday, May 25, 2012 at 17:54 PM, Sébastien Han wrote:
>
> Why don't you use the RabbitMQ builtin cluster solution?
> I setup an active/active cluster with the buildin mecanism and put an
> HAProxy on top with a priority on a specific node. (weight and backup
> options).
>
> For the mirrored queues don't we need to edit the openstack code?
>
> Cheers.
> ~Seb
>
>
>
> On Fri, May 25, 2012 at 10:10 PM, Eric Windisch wrote:
>
> I feel that the best way to deploy RabbitMQ is to run multiple
> independently queue servers and have separate consumers to these servers.
> You can then do client-side balancing to select which Rabbit server
> messages go. To get that in Nova today would be pretty minor -- especially
> after the matchmaker lands (this can provide client-side balancing of
> servers).
>
> --
> Eric Windisch
>
> On Friday, May 25, 2012 at 09:18 AM, Stephen Gran wrote:
>
> Hello,
>
> I am investigating various high availability options for a pending
> deploy of open stack. One of the obvious services to make resilient is
> the mq service. We're going to be using rabbitmq, and we'll most likely
> have N of them in a standard rabbit mq cluster behind a load balancer
> configured as active/passive. One of the obvious improvements on this
> would be to use mirrored queues to protect against message loss as well
> as service downtime.
>
> Are there recommended ways of doing this? I see that I can use durable
> queues, which might work around the problems of openstack checking queue
> parameters on reconnect, but it seems a shame there's not an obvious way
> to do this out of the box. Unless I'm missing something?
>
> Cheers,
> --
> Stephen Gran
> Senior Systems Integrator - guardian.co.uk
>
> Please consider the environment before printing this email.
> --
> Visit guardian.co.uk - newspaper of the year
>
> www.guardian.co.uk www.observer.co.uk www.guardiannews.com
>
> On your mobile, visit m.guardian.co.uk or download the Guardian
> iPhone app www.guardian.co.uk/iphone
>  To save up to 30% when you subscribe to the Guardian and the Observer
> visit www.guardian.co.uk/subscriber
> -
> This e-mail and all attachments are confidential and may also
> be privileged. If you are not the named recipient, please notify
> the sender and delete the e-mail and all attachments immediately.
> Do not disclose the contents to another person. You may not use
> the information for any purpose, or store, or copy, it in any way.
> Guardian News & Media Limited is not liable for any computer
> viruses or other material transmitted with or as part of this
> e-mail. You should employ virus checking software.
>
> Guardian News & Media Limited
>
> A member of Guardian Media Group plc
> Registered Office
> PO Box 68164
> Kings Place
> 90 York Way
> London
> N1P 2AP
>
> Registered in England Number 908396
>
>
> ___
> 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] install cloud computing by openstack!!!

[Sébastien Han]

There are tons of answers by simply googling your issue... and this problem
is more related to the Ubuntu Server mailing but anyway you should try with
the Ubuntu Server 32 bits.

http://www.ubuntu.com/start-download?distro=server&bits=32&release=lts

Or try to enable Intel VT-x or AMD-V from your BIOS (if your processor
supports the extensions).

Hope it helps :)

Cheers.
~Seb.


On Mon, May 28, 2012 at 7:12 PM, Từ Minh Mẫn  wrote:

> I reading document about install:
> http://docs.openstack.org/essex/openstack-compute/starter/content/Base_OS-d1e542.html
>
> I am using Window7 32bit, I want to install server1(64 bit version of
> Ubuntu server 12.04) on Virtual machine (VMWare Workstation 8), When I boot
> VMWare to install Ubuntu, I have problem: "This kernel requires an x86-64
> CPU, but only detected an i686 CPU. Unable to boot – please use a kernel
> appropriate for your CPU"
>
> Please help me to solve this problem!
>
>
> On 28 May 2012 14:49, Razique Mahroua  wrote:
>
>> Yes sorry,
>> my question was intended to Từ Minh Mẫn  :-)
>>
>>
>>   Michael Pittaro 
>>  28 mai 2012 01:41
>> It's really a matter of which Linux distro you prefer (or know better) -
>> the OpenStack pieces are the same everywhere.  I personally work with both
>> Ubuntu _and_ Fedora regularly - but as long as I can run vim and lxde, I'm
>> usually happy with the environment. It's all Linux, after all.
>>
>> I tend to use Ubuntu for openstack development work since the devstack.py
>> toolchain favoured that initially, but I also run Fedora on other
>> machines.
>>
>> mike
>>
>>
>>   Michael Pittaro 
>>  27 mai 2012 19:00
>> On Fri, May 25, 2012 at 12:20 AM, Razique Mahroua
>>
>> The wiki page http://wiki.openstack.org/GetOpenStack lists many of the
>> sources for OpenStack, and there are many links to distribution
>> specific install guides.
>>
>> mike
>>   Razique Mahroua 
>>  25 mai 2012 09:20
>> Hey :-)
>> Please start here :
>> http://docs.openstack.org/essex/openstack-compute/starter/content/
>>
>> And let us know if you have any issues. Also join us on the IRC freenode
>> channel "openstack"
>> Razique
>>
>>
>>   Từ Minh Mẫn 
>>  25 mai 2012 09:07
>> Dear all,
>> I am student of master information, I am a new member of openstack
>> mailing list.
>> This is the first time I study about cloud computing, please help me
>> (step by step - if any) to implement cloud computing, to me can understand
>> and can deployment a system by cloud computing!
>>
>> Thank you so much and best regard!!!
>>
>>
>> --
>>--
>>
>>   Man Tu Minh
>> Mobile   : 0989998815
>>
>> Email : tuminh...@gmail.com tuminh...@yahoo.com.vn
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>> --
>> Nuage & Co - Razique Mahroua
>> razique.mahr...@gmail.com
>>
>>
>>
>>
>
>
> --
>--
>
>   Man Tu Minh
> Mobile   : 0989998815
>
> Email : tuminh...@gmail.com tuminh...@yahoo.com.vn
>
> ___
> 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] rabbit MQ and mirrored queues

[Sébastien Han]

Why don't you use the RabbitMQ builtin cluster solution?
I setup an active/active cluster with the buildin mecanism and put an
HAProxy on top with a priority on a specific node. (weight and backup
options).

For the mirrored queues don't we need to edit the openstack code?

Cheers.
~Seb



On Fri, May 25, 2012 at 10:10 PM, Eric Windisch wrote:

> I feel that the best way to deploy RabbitMQ is to run multiple
> independently queue servers and have separate consumers to these servers.
> You can then do client-side balancing to select which Rabbit server
> messages go. To get that in Nova today would be pretty minor -- especially
> after the matchmaker lands (this can provide client-side balancing of
> servers).
>
> --
> Eric Windisch
>
> On Friday, May 25, 2012 at 09:18 AM, Stephen Gran wrote:
>
> Hello,
>
> I am investigating various high availability options for a pending
> deploy of open stack. One of the obvious services to make resilient is
> the mq service. We're going to be using rabbitmq, and we'll most likely
> have N of them in a standard rabbit mq cluster behind a load balancer
> configured as active/passive. One of the obvious improvements on this
> would be to use mirrored queues to protect against message loss as well
> as service downtime.
>
> Are there recommended ways of doing this? I see that I can use durable
> queues, which might work around the problems of openstack checking queue
> parameters on reconnect, but it seems a shame there's not an obvious way
> to do this out of the box. Unless I'm missing something?
>
> Cheers,
> --
> Stephen Gran
> Senior Systems Integrator - guardian.co.uk
>
> Please consider the environment before printing this email.
> --
> Visit guardian.co.uk - newspaper of the year
>
> www.guardian.co.uk www.observer.co.uk www.guardiannews.com
>
> On your mobile, visit m.guardian.co.uk or download the Guardian
> iPhone app www.guardian.co.uk/iphone
>  To save up to 30% when you subscribe to the Guardian and the Observer
> visit www.guardian.co.uk/subscriber
> -
> This e-mail and all attachments are confidential and may also
> be privileged. If you are not the named recipient, please notify
> the sender and delete the e-mail and all attachments immediately.
> Do not disclose the contents to another person. You may not use
> the information for any purpose, or store, or copy, it in any way.
> Guardian News & Media Limited is not liable for any computer
> viruses or other material transmitted with or as part of this
> e-mail. You should employ virus checking software.
>
> Guardian News & Media Limited
>
> A member of Guardian Media Group plc
> Registered Office
> PO Box 68164
> Kings Place
> 90 York Way
> London
> N1P 2AP
>
> Registered in England Number 908396
>
>
> ___
> 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] Can't ssh into instance

[Sébastien Han]

 debug1: Connection established.
>
>
>>
>> debug1: identity file testkey.pem type -1
>
>
>>
>> debug1: identity file testkey.pem-cert type -1
>
>
>>
>> debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 
>> Debian-7ubuntu1
>
>
>>
>> debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH*
>
>
>>
>> debug1: Enabling compatibility mode for protocol 2.0
>
>
>>
>> debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
>
>
>>
>> debug1: SSH2_MSG_KEXINIT sent
>
>
>>
>> Read from socket failed: Connection reset by peer
>
>
>
>
> " Connection reset by peer " after "debug1: SSH2_MSG_KEXINIT sent" it looks 
> like network issue.
>
>
>
> Anyway thank you very much.
>
>
>
> On Fri, May 25, 2012 at 3:19 AM, Sébastien Han wrote:
>
>> Ok ok, no offense in my previous emails :)
>> Good to know that everything is working.
>>
>> Cheers.
>>
>>
>>
>>
>> On Fri, May 25, 2012 at 1:00 AM, Leander Bessa Beernaert <
>> leande...@gmail.com> wrote:
>>
>>> I'm in no way saying that openstack is to blame for the current problem,
>>> but it occurred to me that my install could have script failed somewhere
>>> along the way without me knowing (i might have forgotten to mention that in
>>> the previous post :s).
>>>
>>> Adding those two lines solved my problem.  I've already mentioned it
>>> earlier, perhaps the mail wasn't sent to the list. And yes, i'm still using
>>> a all-in-one setup for now.
>>>
>>>  Thanks for the tip.
>>>
>>>
>>> On Thu, May 24, 2012 at 9:03 PM, Sébastien Han 
>>> wrote:
>>>
>>>> Why did you reinstall everything?
>>>> There is no "just in case", I mean you solved your issue, it was from
>>>> your configuration not from openstack :)
>>>>
>>>> It's a routing issue, same as earlier.
>>>> Check again those parameters, specially the first one:
>>>>
>>>>- --routing_source_ip=IP_CURRENT_NODE
>>>>- --my_ip=IP_CURRENT_NODE
>>>>
>>>> Still in all-in-one setup?
>>>>
>>>> Cheers :)
>>>>
>>>> On Thu, May 24, 2012 at 8:40 PM, Matt Joyce <
>>>> matt.jo...@cloudscaling.com> wrote:
>>>>
>>>>> First rule of security group.  Do not talk about security group.  
>>>>>
>>>>>
>>>>> On Thu, May 24, 2012 at 9:35 AM, Rogerio Goncalves 
>>>>> wrote:
>>>>>
>>>>>> Maybe you missed the rules of security group?
>>>>>>
>>>>>> Rogério Gonçalves
>>>>>> roge...@gmail.com
>>>>>> Cel: (11) 8840-9790
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, May 24, 2012 at 12:12 PM, Leander Bessa Beernaert <
>>>>>> leande...@gmail.com> wrote:
>>>>>>
>>>>>>> I've formatted the host machine and reinstalled openstack, just in
>>>>>>> case. Now i am only getting "connection refused".
>>>>>>>
>>>>>>>
>>>>>>> On Thu, May 24, 2012 at 3:01 PM, Leander Bessa Beernaert <
>>>>>>> leande...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Compute log: Log: http://paste.openstack.org/show/18149/
>>>>>>>>
>>>>>>>> I've tried bot root and ubuntu as account names (ssh -i key.pem
>>>>>>>> root@10.1.2.3 and  ssh -i key.pem ubuntu@10.1.2.3) and the result
>>>>>>>> is still "Read from socket failed: Connection reset by peer"
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert <
>>>>>>>> leande...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Complete log: http://paste.openstack.org/show/18144/
>>>>>>>>>
>>>>>>>>> On Thu, May 24, 2012 at 1:49 PM, Anton Haldin <
>>>>>>>>> ahal...@griddynamics.com> wrote:
>>>>>>>>>
>>>>>>>>>> you can try to look in  con

[Openstack] Can't attach a RBD volume to an instance

[Sébastien Han]

Hi everyone,

I setup a ceph cluster and I use the RBD driver for nova-volume.
I can create volumes and snapshots but currently I can't attach them to an
instance.
Apparently the volume is detected as busy but it's not, no matter which
name I choose.
I tried from horizon and the command line, same issue.

$ nova --debug volume-attach de3743be-69be-4ec3-8de3-fc7df6903a97 12
/dev/vdc
connect: (localhost, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
localhost:5000\r\nContent-Length: 100\r\ncontent-type:
application/json\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nuser-agent: python-novaclient\r\n\r\n{"auth":
{"tenantName": "admin", "passwordCredentials": {"username": "admin",
"password": "admin"}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Fri, 25 May 2012 08:29:46 GMT
header: Transfer-Encoding: chunked
connect: (172.17.1.6, 8774)
send: u'GET
/v2/d1f5d27ccf594cdbb034c8a4123494e9/servers/de3743be-69be-4ec3-8de3-fc7df6903a97
HTTP/1.1\r\nHost: 172.17.1.6:8774\r\nx-auth-project-id:
admin\r\nx-auth-token: 37ff6354b9114178889128175494c666\r\naccept-encoding:
gzip, deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-fc7686dd-7dff-4ea2-b2dd-be584dadb7c1
header: Content-Type: application/json
header: Content-Length: 1371
header: Date: Fri, 25 May 2012 08:29:46 GMT
send: u'POST
/v2/d1f5d27ccf594cdbb034c8a4123494e9/servers/de3743be-69be-4ec3-8de3-fc7df6903a97/os-volume_attachments
HTTP/1.1\r\nHost: 172.17.1.6:8774\r\nContent-Length:
60\r\nx-auth-project-id: admin\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nx-auth-token:
37ff6354b9114178889128175494c666\r\nuser-agent:
python-novaclient\r\ncontent-type:
application/json\r\n\r\n{"volumeAttachment": {"device": "/dev/vdc",
"volumeId": 12}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-4a22f603-4aad-4ae9-99a2-6a7bcacf974f
header: Content-Type: application/json
header: Content-Length: 48
header: Date: Fri, 25 May 2012 08:29:46 GMT


$ echo $?
0

See the logs here:
http://paste.openstack.org/show/18163/

If you need more information let me know :)
Thank you in advance.

Cheers.

~Seb
___
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] Can't ssh into instance

[Sébastien Han]

Ok ok, no offense in my previous emails :)
Good to know that everything is working.

Cheers.



On Fri, May 25, 2012 at 1:00 AM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> I'm in no way saying that openstack is to blame for the current problem,
> but it occurred to me that my install could have script failed somewhere
> along the way without me knowing (i might have forgotten to mention that in
> the previous post :s).
>
> Adding those two lines solved my problem.  I've already mentioned it
> earlier, perhaps the mail wasn't sent to the list. And yes, i'm still using
> a all-in-one setup for now.
>
>  Thanks for the tip.
>
>
> On Thu, May 24, 2012 at 9:03 PM, Sébastien Han wrote:
>
>> Why did you reinstall everything?
>> There is no "just in case", I mean you solved your issue, it was from
>> your configuration not from openstack :)
>>
>> It's a routing issue, same as earlier.
>> Check again those parameters, specially the first one:
>>
>>- --routing_source_ip=IP_CURRENT_NODE
>>- --my_ip=IP_CURRENT_NODE
>>
>> Still in all-in-one setup?
>>
>> Cheers :)
>>
>> On Thu, May 24, 2012 at 8:40 PM, Matt Joyce 
>> wrote:
>>
>>> First rule of security group.  Do not talk about security group.  
>>>
>>>
>>> On Thu, May 24, 2012 at 9:35 AM, Rogerio Goncalves wrote:
>>>
>>>> Maybe you missed the rules of security group?
>>>>
>>>> Rogério Gonçalves
>>>> roge...@gmail.com
>>>> Cel: (11) 8840-9790
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, May 24, 2012 at 12:12 PM, Leander Bessa Beernaert <
>>>> leande...@gmail.com> wrote:
>>>>
>>>>> I've formatted the host machine and reinstalled openstack, just in
>>>>> case. Now i am only getting "connection refused".
>>>>>
>>>>>
>>>>> On Thu, May 24, 2012 at 3:01 PM, Leander Bessa Beernaert <
>>>>> leande...@gmail.com> wrote:
>>>>>
>>>>>> Compute log: Log: http://paste.openstack.org/show/18149/
>>>>>>
>>>>>> I've tried bot root and ubuntu as account names (ssh -i key.pem
>>>>>> root@10.1.2.3 and  ssh -i key.pem ubuntu@10.1.2.3) and the result is
>>>>>> still "Read from socket failed: Connection reset by peer"
>>>>>>
>>>>>>
>>>>>> On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert <
>>>>>> leande...@gmail.com> wrote:
>>>>>>
>>>>>>>
>>>>>>> Complete log: http://paste.openstack.org/show/18144/
>>>>>>>
>>>>>>> On Thu, May 24, 2012 at 1:49 PM, Anton Haldin <
>>>>>>> ahal...@griddynamics.com> wrote:
>>>>>>>
>>>>>>>> you can try to look in  console.log for this instance
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert <
>>>>>>>> leande...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> No, at the moment the vnc console isn't working yet. I haven't
>>>>>>>>> gotten that far yet.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, May 24, 2012 at 1:29 PM, Anton Haldin <
>>>>>>>>> ahal...@griddynamics.com> wrote:
>>>>>>>>>
>>>>>>>>>> t can be an issue on OS side in instance ?
>>>>>>>>>>
>>>>>>>>>> do you have vnc access for this instance?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert <
>>>>>>>>>> leande...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> I'm having trouble sshing into the created instances. At first i
>>>>>>>>>>> was getting the following error:
>>>>>>>>>>>
>>>>>>>>>>> ssh -i testkey.pem root@10.1.1.3 -v
>>>>>>>>>

Re: [Openstack] Can't ssh into instance

[Sébastien Han]

Why did you reinstall everything?
There is no "just in case", I mean you solved your issue, it was from your
configuration not from openstack :)

It's a routing issue, same as earlier.
Check again those parameters, specially the first one:

   - --routing_source_ip=IP_CURRENT_NODE
   - --my_ip=IP_CURRENT_NODE

Still in all-in-one setup?

Cheers :)

On Thu, May 24, 2012 at 8:40 PM, Matt Joyce wrote:

> First rule of security group.  Do not talk about security group.  
>
>
> On Thu, May 24, 2012 at 9:35 AM, Rogerio Goncalves wrote:
>
>> Maybe you missed the rules of security group?
>>
>> Rogério Gonçalves
>> roge...@gmail.com
>> Cel: (11) 8840-9790
>>
>>
>>
>>
>> On Thu, May 24, 2012 at 12:12 PM, Leander Bessa Beernaert <
>> leande...@gmail.com> wrote:
>>
>>> I've formatted the host machine and reinstalled openstack, just in case.
>>> Now i am only getting "connection refused".
>>>
>>>
>>> On Thu, May 24, 2012 at 3:01 PM, Leander Bessa Beernaert <
>>> leande...@gmail.com> wrote:
>>>
 Compute log: Log: http://paste.openstack.org/show/18149/

 I've tried bot root and ubuntu as account names (ssh -i key.pem
 root@10.1.2.3 and  ssh -i key.pem ubuntu@10.1.2.3) and the result is
 still "Read from socket failed: Connection reset by peer"


 On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert <
 leande...@gmail.com> wrote:

>
> Complete log: http://paste.openstack.org/show/18144/
>
> On Thu, May 24, 2012 at 1:49 PM, Anton Haldin <
> ahal...@griddynamics.com> wrote:
>
>> you can try to look in  console.log for this instance
>>
>>
>>
>> On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert <
>> leande...@gmail.com> wrote:
>>
>>> No, at the moment the vnc console isn't working yet. I haven't
>>> gotten that far yet.
>>>
>>>
>>> On Thu, May 24, 2012 at 1:29 PM, Anton Haldin <
>>> ahal...@griddynamics.com> wrote:
>>>
 t can be an issue on OS side in instance ?

 do you have vnc access for this instance?


 On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert <
 leande...@gmail.com> wrote:

> Hello,
>
> I'm having trouble sshing into the created instances. At first i
> was getting the following error:
>
> ssh -i testkey.pem root@10.1.1.3 -v
>>
>> OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
>>
>> debug1: Reading configuration data /etc/ssh/ssh_config
>>
>> debug1: /etc/ssh/ssh_config line 19: Applying options for *
>>
>> debug1: Connecting to 10.1.1.3 [10.1.1.3] port 22.
>>
>> debug1: Connection established.
>>
>> debug1: identity file testkey.pem type -1
>>
>> debug1: identity file testkey.pem-cert type -1
>>
>> debug1: Remote protocol version 2.0, remote software version
>>> OpenSSH_5.8p1 Debian-7ubuntu1
>>
>> debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH*
>>
>> debug1: Enabling compatibility mode for protocol 2.0
>>
>> debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
>>
>> debug1: SSH2_MSG_KEXINIT sent
>>
>> Read from socket failed: Connection reset by peer
>>
>>
> I then proceeded to reboot the machine and all it's services.
> However, now i can't even get that far. I'm alway faced with a 
> connection
> refused.
>
> I've added the permissions for port 22 and icmp in the default
> security group and i'm also able to ping the instances.
>
> I'm using the openstack packages provided with ubuntu 12.04.
>
> Regards,
>
> Leander
>
> ___
> 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
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.la

Re: [Openstack] Can't ssh into instance

[Sébastien Han]

Perfect!
Yes in a multi-host scenario it's the IP address of the compute node itself
:)

Cheers!

On Thu, May 24, 2012 at 5:34 PM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> Just a question i forgot, on a multi-host senario, the IP_CURRENT_NODE is
> the compute node's ip right? Currently i'm only running everything on a
> single host.
>
>
> On Thu, May 24, 2012 at 4:32 PM, Leander Bessa Beernaert <
> leande...@gmail.com> wrote:
>
>> Adding the following to my config file solved my problem!! Thanks!!
>>
>>- routing_source_ip=IP_CURRENT_NODE
>>- --my_ip=IP_CURRENT_NODE
>>
>> Regards,
>>
>> Leander
>>
>> On Thu, May 24, 2012 at 4:24 PM, Sébastien Han 
>> wrote:
>>
>>> It's not an open-ssh issue.
>>> Your virtual machine simply can't fetch the metadata, cloud-init can't
>>> to be more accurate. Without this your ssh key is not imported. This is why
>>> the machine is well running, you can ping it but you can't access it
>>> because the authorized_keys file on the vm is not fulfill.
>>> If you are only running a nova-compute node, installing
>>> nova-api-metadata will do the trick!
>>>
>>> Also verify those values in your nova.conf :
>>>
>>>- --vncserver_proxyclient_address=IP_CURRENT_NODE
>>>- --vncserver_listen=IP_CURRENT_NODE
>>>- --ec2_dmz_host=IP_CURRENT_NODE
>>>- --routing_source_ip=IP_CURRENT_NODE
>>>- --my_ip=IP_CURRENT_NODE
>>>
>>> Let us know a little more about your setup :)
>>> Cheers!
>>>
>>>
>>>
>>> On Thu, May 24, 2012 at 4:01 PM, Leander Bessa Beernaert <
>>> leande...@gmail.com> wrote:
>>>
>>>> Compute log: Log: http://paste.openstack.org/show/18149/
>>>>
>>>> I've tried bot root and ubuntu as account names (ssh -i key.pem
>>>> root@10.1.2.3 and  ssh -i key.pem ubuntu@10.1.2.3) and the result is
>>>> still "Read from socket failed: Connection reset by peer"
>>>>
>>>>
>>>> On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert <
>>>> leande...@gmail.com> wrote:
>>>>
>>>>>
>>>>> Complete log: http://paste.openstack.org/show/18144/
>>>>>
>>>>> On Thu, May 24, 2012 at 1:49 PM, Anton Haldin <
>>>>> ahal...@griddynamics.com> wrote:
>>>>>
>>>>>> you can try to look in  console.log for this instance
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert <
>>>>>> leande...@gmail.com> wrote:
>>>>>>
>>>>>>> No, at the moment the vnc console isn't working yet. I haven't
>>>>>>> gotten that far yet.
>>>>>>>
>>>>>>>
>>>>>>> On Thu, May 24, 2012 at 1:29 PM, Anton Haldin <
>>>>>>> ahal...@griddynamics.com> wrote:
>>>>>>>
>>>>>>>> t can be an issue on OS side in instance ?
>>>>>>>>
>>>>>>>> do you have vnc access for this instance?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert <
>>>>>>>> leande...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> I'm having trouble sshing into the created instances. At first i
>>>>>>>>> was getting the following error:
>>>>>>>>>
>>>>>>>>> ssh -i testkey.pem root@10.1.1.3 -v
>>>>>>>>>>
>>>>>>>>>> OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
>>>>>>>>>>
>>>>>>>>>> debug1: Reading configuration data /etc/ssh/ssh_config
>>>>>>>>>>
>>>>>>>>>> debug1: /etc/ssh/ssh_config line 19: Applying options for *
>>>>>>>>>>
>>>>>>>>>> debug1: Connecting to 10.1.1.3 [10.1.1.3] port 22.
>>>>>>>>>>
>>>>>>>>>> debug1: Connection established.
>>>>>>>>>>
>>>>>>>>>> debug1

Re: [Openstack] Can't ssh into instance

[Sébastien Han]

It's not an open-ssh issue.
Your virtual machine simply can't fetch the metadata, cloud-init can't to
be more accurate. Without this your ssh key is not imported. This is why
the machine is well running, you can ping it but you can't access it
because the authorized_keys file on the vm is not fulfill.
If you are only running a nova-compute node, installing nova-api-metadata
will do the trick!

Also verify those values in your nova.conf :

   - --vncserver_proxyclient_address=IP_CURRENT_NODE
   - --vncserver_listen=IP_CURRENT_NODE
   - --ec2_dmz_host=IP_CURRENT_NODE
   - --routing_source_ip=IP_CURRENT_NODE
   - --my_ip=IP_CURRENT_NODE

Let us know a little more about your setup :)
Cheers!


On Thu, May 24, 2012 at 4:01 PM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> Compute log: Log: http://paste.openstack.org/show/18149/
>
> I've tried bot root and ubuntu as account names (ssh -i key.pem
> root@10.1.2.3 and  ssh -i key.pem ubuntu@10.1.2.3) and the result is
> still "Read from socket failed: Connection reset by peer"
>
>
> On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert <
> leande...@gmail.com> wrote:
>
>>
>> Complete log: http://paste.openstack.org/show/18144/
>>
>> On Thu, May 24, 2012 at 1:49 PM, Anton Haldin 
>> wrote:
>>
>>> you can try to look in  console.log for this instance
>>>
>>>
>>>
>>> On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert <
>>> leande...@gmail.com> wrote:
>>>
 No, at the moment the vnc console isn't working yet. I haven't gotten
 that far yet.


 On Thu, May 24, 2012 at 1:29 PM, Anton Haldin >>> > wrote:

> t can be an issue on OS side in instance ?
>
> do you have vnc access for this instance?
>
>
> On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert <
> leande...@gmail.com> wrote:
>
>> Hello,
>>
>> I'm having trouble sshing into the created instances. At first i was
>> getting the following error:
>>
>> ssh -i testkey.pem root@10.1.1.3 -v
>>>
>>> OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
>>>
>>> debug1: Reading configuration data /etc/ssh/ssh_config
>>>
>>> debug1: /etc/ssh/ssh_config line 19: Applying options for *
>>>
>>> debug1: Connecting to 10.1.1.3 [10.1.1.3] port 22.
>>>
>>> debug1: Connection established.
>>>
>>> debug1: identity file testkey.pem type -1
>>>
>>> debug1: identity file testkey.pem-cert type -1
>>>
>>> debug1: Remote protocol version 2.0, remote software version
 OpenSSH_5.8p1 Debian-7ubuntu1
>>>
>>> debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH*
>>>
>>> debug1: Enabling compatibility mode for protocol 2.0
>>>
>>> debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
>>>
>>> debug1: SSH2_MSG_KEXINIT sent
>>>
>>> Read from socket failed: Connection reset by peer
>>>
>>>
>> I then proceeded to reboot the machine and all it's services.
>> However, now i can't even get that far. I'm alway faced with a connection
>> refused.
>>
>> I've added the permissions for port 22 and icmp in the default
>> security group and i'm also able to ping the instances.
>>
>> I'm using the openstack packages provided with ubuntu 12.04.
>>
>> Regards,
>>
>> Leander
>>
>> ___
>> 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] [Dashboard] Can't access images/snapshots

[Sébastien Han]

Hi,

Do you also have an error when retrieving from the command line?

~Cheers!



On Wed, May 16, 2012 at 5:38 PM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> Hello,
>
> I keep running into this error when i try to list the images/snapshot in
> dashboard: http://paste.openstack.org/show/17820/
>
> This is my local_settings.py file: http://paste.openstack.org/show/17822/ ,
> am i missing something?
>
> Regards,
>
> Leander
>
> ___
> 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] Nova volume storage

[Sébastien Han]

Thank you for your answers.

Apparently there are some fans of RDB even if I omitted this one.
But as I know it's not release as 1.0 yet.

So does RDB ready and enough stable for production? (out of the box)

Thank you!


On Sun, May 6, 2012 at 1:07 PM, Tomasz Paszkowski  wrote:

> Yes. I works perfectly (with xfs as storage backend).
>
> On Sun, May 6, 2012 at 9:30 AM, Igor Laskovy 
> wrote:
> > Privet Tomasz,
> >
> > Do you use rbd in production? Any restrictions?
> >
> > On Sat, May 5, 2012 at 9:50 PM, Tomasz Paszkowski 
> wrote:
> >> ceph (known as rbd) :-)
> >>
> >>
> >> On Sat, May 5, 2012 at 6:06 PM, Sébastien Han 
> wrote:
> >>> Hi everyone!
> >>>
> >>> I was wondering which kind of backend storage are you using for your
> >>> nova-volume?
> >>>
> >>> I found a lot of solutions like:
> >>>
> >>> LVM local
> >>> Sheepdog
> >>> Nexenta for NFS or NFS itself
> >>> SAN
> >>> GlusterFS
> >>> NetApp
> >>>
> >>> Any ideas? Feedback?
> >>>
> >>> I like the GlusterFS ability to use both NFS and GlusterFS as mount
> point
> >>> for client. They also have this 'OSConnect' functionality which
> provides
> >>> connectivity to nova-volume and apparently performs live migration
> without
> >>> downtime.
> >>>
> >>> 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
> >>>
> >>
> >>
> >>
> >> --
> >> Tomasz Paszkowski
> >> SS7, Asterisk, SAN, Datacenter, Cloud Computing
> >> +48500166299
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~openstack
> >> Post to : openstack@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~openstack
> >> More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> > --
> > Igor Laskovy
>
>
>
> --
> Tomasz Paszkowski
> SS7, Asterisk, SAN, Datacenter, Cloud Computing
> +48500166299
>
> ___
> 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] Nova volume storage

[Sébastien Han]

Hi everyone!

I was wondering which kind of backend storage are you using for your
nova-volume?

I found a lot of solutions like:

   - LVM local
   - Sheepdog
   - Nexenta for NFS or NFS itself
   - SAN
   - GlusterFS
   - NetApp

Any ideas? Feedback?

I like the GlusterFS ability to use both NFS and GlusterFS as mount point
for client. They also have this 'OSConnect' functionality which provides
connectivity to nova-volume and apparently performs live migration without
downtime.

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

Re: [Openstack] Has anyone tested Juju with 12.04 Essex installation?

[Sébastien Han]

Hi!

I'm sorry but I can't helpyou, however I'm very interested in your setup.
I'm also using Juju combined to MAAS. I have some issues at the moment
(juju status, ssh keys and so on...)

Are you also working on Bare Metal or on EC2 instances?

Cheers!


On Thu, May 3, 2012 at 3:04 PM, Jorge Luiz Correa wrote:

> Hi list!
>
> I would like to know if someone has tested juju with Essex. I've installed
> OpenStack using Ubuntu 12.04 and its packages (Essex). The nova components
> are working fine. I can create and destroy instances. So I'm using Juju
> from a 11.10 Oneiric. I've made some modifications in my environment.yaml
> configuration file to work with keystone. In my first tests I could
> bootstrap, creating a new instance. However, some problems that I'm having
> now:
>
> 1) Juju and nova aren't creating secgroup-rules in the right way. I can
> see new secgroup-rules, like juju-sample, juju-sample-0 and so on. But,
> when I list the rules, there are NO rules. The immediately impact is that
> when running 'juju status' the host is not able to access the instances
> created by juju. If I go to dashboard and add access with the right ports,
> so juju gets working.
>
> 2) The host running juju 'should' know how to resolve the instance names,
> like server-8, server-10 to address from cloud network. How we need to deal
> with it? Host running juju has to use the same DNS that serves the cloud?
> I've changed the dhcp configuration in juju host to add the address of nova
> network that runs a dnsmasq and knows how to resolve these names. Is this
> the right way? Recommendations?
>
> Thanks!
>
> --
> - MSc. Correa, J.L.
>
>
> ___
> 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] OpenStack immaturity

[Sébastien Han]

Hi everyone,

According to the statement of this article from Gartner group
http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/
Openstack is a
highly immature platform.
But why? What's make Openstack so immature?

Any comments on that?

Thank you in advance :)
___
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] Howto Nova setup with HA?

[Sébastien Han]

Hi Tristan,

When I saw your post, I though what about an pacemaker ressource agent?
Corosync for the messaging layer and pacemaker for the ressource
management. Maybe someone as wrote a script ressource agent for nova in
order to manage the failover.
Also DRBD can be useful.
And then after a couple of research on Google, I found this 3 links:

   - https://lists.launchpad.net/openstack/pdfGiNwMEtUBJ.pdf
   - http://wiki.openstack.org/HAforNovaDB
   - http://www.pixelbeat.org/docs/pacemaker-cloud/

Hope this will help you.

--
Yours sincerely.
Sébastien HAN.



On Tue, Feb 14, 2012 at 12:05 PM, i3D.net - Tristan van Bokkem <
tristanvanbok...@i3d.nl> wrote:

> **
> Hi Christian,
>
> Thanks for your reply.
>
> With mysql master/master i meant the following: http://mysql-mmm.org/ but
> it seems they are using 2 different locations for mysql reads and writes.
> Something nova is (yet) not able to configure (i.e. --sql_connection= which
> is being used for reads and rights.)
>
> Maybe http://www.mysql.com/products/cluster/ is a better way..
>
> RabbitMQ HA i am aware of. This is something we are looking at as well.
>
> The main question is how does other companies reach HA with openstack? I
> can't find any good information on the net about it.
> And how does Essex change things?
>
>
> Best regards,
>
> Tristan van Bokkem
> Datacenter Operations
>
> Contact:
> E-mail Personal: tristanvanbok...@i3d.net
> E-mail Support: i...@i3d.net
> E-mail NOC: n...@i3d.net
> Website: http://www.i3d.net Office:
> Interactive 3D B.V.
> Meent 93b
> 3011 JG Rotterdam
> The Netherlands
>
> Visit www.smartdc.net – SmartDC is our in-house 36,000 sq. ft. datacenter
> in Rotterdam, The Netherlands. High density hosting – multiple fiber
> carriers in-house – Level3 PoP.
>
> Interactive 3D (i3D.net) is a company registered in The Netherlands at
> Meent 93b, Rotterdam. Registration #: 14074337 - VAT # NL 8202.63.886.B01.
> Interactive 3D (i3D.net) is CDSA certified on content protection and
> security. We are ranked in the Deloitte Technology Fast 50 as one of the
> fastest growing technology companies.
>
> --
> *From:* Christian Berendt [mailto:bere...@b1-systems.de]
> *To:* i3D.net - Tristan van Bokkem [mailto:tristanvanbok...@i3d.nl]
> *Cc:* openstack@lists.launchpad.net
> *Sent:* Tue, 14 Feb 2012 11:54:38 +0100
> *Subject:* Re: [Openstack] Howto Nova setup with HA?
>
>
> Hi Tristan.
>
> > So, we can run MySQL in master-master mode on multiple hosts, we can
> > run nova-api on serveral hosts and load balance those and RabbitMQ
> > has a cluster ha setup as well but is this the way to go? I can't
> > find a clear answer to this. I am hoping one can shine some light on
> > this!
>
> I would prefer to use MySQL Cluster:
> http://www.mysql.com/products/cluster/. You meant that with MySQL
> master-master?
>
> For RabbitMQ there are several ways to setup it:
> http://www.rabbitmq.com/ha.html.
>
> I think the customer site has to decide which HA setup they want use.
> All types have advantages and disadvantages.
>
> HTH, Christian.
>
> --
> Christian Berendt
> Linux / Unix Consultant & Developer
> Mail: bere...@b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
>
> ___
> 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