[Openstack] Can't start instance after upgrade to Mitaka release

2016-04-20 Thread K K
Hello. I upgraded release OpenStack from Kilo to Mitaka. But now I can't start any Instance. At the compute node nova daemons said: 2016-04-20 12:40:15.395 226509 ERROR oslo_messaging.rpc.dispatcher [req-86e4ab2e-229a-438d-87d2-d9ce9f749dbc 79401c3a746740ef826762ca9eaeb207 3029462986ac400ca2c2c6

Re: [Openstack] Can't start instance after upgrade to Mitaka release

2016-04-20 Thread K K
okey. Yes, it's a trouble. I solved that problem by add use_neutron = true to nova.conf at compute and controller nodes. Also I added to nova.conf@compute  node: [neutron] auth_type = password auth_url = http://controller:35357 But now I get else error when I try to start instance. Nova@compute0

Re: [Openstack] Can't start instance after upgrade to Mitaka release

2016-04-21 Thread K K
= neutron >password = NEUTRON_PASS >---cut here--- > >You should try to follow all steps from the install guide [1], the >option "use_neutron" is new since Mitaka and it's mentioned there. > > >[1] >http://docs.openstack.org/mitaka/install-guide-obs

[Openstack] nova backup

2016-04-21 Thread K K
Hello. When I try to create backup: nova backup testdeb testdeb_bak daily 2 nova-api said: ==> nova/nova-api.log <== 2016-04-21 16:40:14.828 2814 INFO nova.compute.api [req-e89878e7-9d26-4e6e-8922-8aa9bba56b72 8d384cc45d0c467eb46ef3f980cf314d 3029462986ac400ca2c2c6ac4c9af5a7 - - -] [instance: a

Re: [Openstack] nova backup

2016-04-21 Thread K K
ly you launched that instance via boot-from-volume, so your >instance's image resides within a volume, and volumes are handled by >cinder. So these instances should be backed up via cinder. > >Eugen > > >Zitat von K K < n...@mail.ru >: > >> Hello. >> When

[Openstack] [cinder] incremental backup to ceph backup cluster

2016-04-25 Thread K K
Hello, there I'm trying to create incremental backup to 2nd Ceph cluster, but all backups on those cluster are full. Can anybody tell my why? My steps are: 1. cinder backup-create --force 46a306ae-2454-4425-a6f7-96d7c02acc95 2. cinder backup-create --incremental --force 46a306ae-2454-4425-a6f7