Re: [Openstack] can I manually register a volume in cinder

2016-07-11 Thread Avishay Traeger
Yes, you can do this with the "cinder manage" command.  The syntax should
be:

cinder manage --id-type source-name  
Where:
 is the name of your Ceph Cinder backend (you can run "cinder-manage
host list" to get this)
 is the name of the volume on the Ceph backend

You can also optionally specify name, description, volume type,
availability zone, metadata, and bootable flag in the same command.


On Mon, Jul 11, 2016 at 5:42 PM, yang sheng  wrote:

> Hi
> I am using openstack liberty with ceph jewel.
>
> All the glance images and cinder volumes are stored in ceph pools (images
> and volumes pools)
>
> I have some volumes in the ceph volumes pool but not registered in cinder
> (database).
>
> Is there anyway I can manually register these volumes (in ceph volumes
> pool) in the cinder?
>
> thanks
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
*Avishay Traeger, PhD*
*System Architect*

Mobile: +972 54 447 1475
E-mail: avis...@stratoscale.com



Web  | Blog 
 | Twitter  | Google+

 | Linkedin 
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


[Openstack] [Sahara]Cloudera-manager fail to start when deploy cdh cluster

2016-07-11 Thread fuguangping
Hi All,


I am a new sahara user, and I download cdh plugin image from 
http://sahara-files.mirantis.com/images/upstream/liberty/. 


Unfortunately, When I try to create a cdh-5.4 cluster, the cloudera-manager 
always fail to start. I ssh to the manager server, and try to start by hand, 
the "cloudera-scm-server.log" shows following error:


org.hibernate.service.classloading.spi.ClassLoadingException: HHH010003: JDBC 
Driver class not found: com.mysql.jdbc.Driver
 
I download the mysql driver and copy  to "/usr/share/cmf/lib", it seems to 
work, but to my surprise the service die after a while. I check the log again, 
and find the following error:


org.hibernate.exception.GenericJDBCException: Could not open connection
java.sql.SQLException: Connections could not be acquired from the underlying 
database!


I'm not sure if these is some bugs in the images or I miss some configurations. 
Is anyone meet similar issue? How to fix this error without modify the image? 


Thanks!



Regards,

Guangping Fu___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] Quesion about Openstack Magnum

2016-07-11 Thread John Belamaric
I had a similar issue. If you follow the guide you use "container-infra” for 
the service type, but the magnum client version I was using (2.1.0) looks for 
”container”.

Even after that though, I have not been able to get it fully working. I am 
seeing this error in magnum-conductor.log, and haven’t had time to fully debug 
it:


2016-07-11 16:13:08.433 19996 DEBUG oslo_service.periodic_task [-] Running 
periodic task MagnumPeriodicTasks._send_bay_metrics run_periodic_tasks 
/var/lib/magnum/env/local/lib/python2.7/site-packages/oslo_service/periodic_task.py:215
2016-07-11 16:13:08.434 19996 DEBUG magnum.service.periodic 
[req-428e2bcc-06be-4745-adb0-d1a8df08af0c - - - - -] Starting to send bay 
metrics _send_bay_metrics 
/var/lib/magnum/env/local/lib/python2.7/site-packages/magnum/service/periodic.py:149
2016-07-11 16:13:08.953 19996 DEBUG oslo_service.periodic_task [-] Running 
periodic task MagnumServicePeriodicTasks.update_magnum_service 
run_periodic_tasks 
/var/lib/magnum/env/local/lib/python2.7/site-packages/oslo_service/periodic_task.py:215
2016-07-11 16:13:08.953 19996 DEBUG magnum.servicegroup.magnum_service_periodic 
[req-d9472221-3976-4ea7-bb8c-78901476bb5d - - - - -] Update magnum_service 
update_magnum_service 
/var/lib/magnum/env/local/lib/python2.7/site-packages/magnum/servicegroup/magnum_service_periodic.py:42
2016-07-11 16:13:09.026 19996 DEBUG oslo_service.periodic_task [-] Running 
periodic task MagnumPeriodicTasks.sync_bay_status run_periodic_tasks 
/var/lib/magnum/env/local/lib/python2.7/site-packages/oslo_service/periodic_task.py:215
2016-07-11 16:13:09.026 19996 DEBUG magnum.service.periodic 
[req-3e18d7b3-851c-4d5b-9ef6-28b70528c7a2 - - - - -] Starting to sync up bay 
status sync_bay_status 
/var/lib/magnum/env/local/lib/python2.7/site-packages/magnum/service/periodic.py:71
2016-07-11 16:13:09.059 19996 WARNING magnum.common.keystone 
[req-3e18d7b3-851c-4d5b-9ef6-28b70528c7a2 - - - - -] Auth plugin and its 
options for service user must be provided in [keystone_auth] section. Using 
values from [keystone_authtoken] section is deprecated.
2016-07-11 16:13:09.146 19996 WARNING magnum.service.periodic 
[req-3e18d7b3-851c-4d5b-9ef6-28b70528c7a2 - - - - -] Ignore error [unexpected 
keystone client error occurred: Expecting to find id or name in user - the 
server could not comply with the request since it is either malformed or 
otherwise incorrect. The client is assumed to be in error. (HTTP 400) 
(Request-ID: req-69b34d03-d052-47c1-b096-6abf01ad1fe8)] when syncing up bay 
status.
2016-07-11 16:13:09.146 19996 ERROR magnum.service.periodic Traceback (most 
recent call last):
2016-07-11 16:13:09.146 19996 ERROR magnum.service.periodic   File 
"/var/lib/magnum/env/local/lib/python2.7/site-packages/magnum/service/periodic.py",
 line 83, in sync_bay_status
2016-07-11 16:13:09.146 19996 ERROR magnum.service.periodic stacks = 
osc.heat().stacks.list(global_tenant=True,
2016-07-11 16:13:09.146 19996 ERROR magnum.service.periodic   File 
"/var/lib/magnum/env/local/lib/python2.7/site-packages/magnum/common/exception.py",
 line 66, in wrapped
2016-07-11 16:13:09.146 19996 ERROR magnum.service.periodic % 
sys.exc_info()[1])
2016-07-11 16:13:09.146 19996 ERROR magnum.service.periodic 
AuthorizationFailure: unexpected keystone client error occurred: Expecting to 
find id or name in user - the server could not comply with the request since it 
is either malformed or otherwise incorrect. The client is assumed to be in 
error. (HTTP 400) (Request-ID: req-69b34d03-d052-47c1-b096-6abf01ad1fe8)
2016-07-11 16:13:09.146 19996 ERROR magnum.service.periodic



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] can I manually register a volume in cinder

2016-07-11 Thread Lomayani S. Laizer
I think you can create empty volumes in cinder command line of the same as
your volume. then delete created volume in ceph. finally rename you volume
with data in ceph to deleted volume name created in cinder

 cinder create --name volume_name  volume_size

 rbd rm pool_name/volume-id_of_cinder_volume)

 rbd rename pool_name/your_volume_name  pool_name/volume-id_of_cinder_volume


--
Lomayani

On Mon, Jul 11, 2016 at 5:42 PM, yang sheng  wrote:

> Hi
> I am using openstack liberty with ceph jewel.
>
> All the glance images and cinder volumes are stored in ceph pools (images
> and volumes pools)
>
> I have some volumes in the ceph volumes pool but not registered in cinder
> (database).
>
> Is there anyway I can manually register these volumes (in ceph volumes
> pool) in the cinder?
>
> thanks
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


[Openstack] can I manually register a volume in cinder

2016-07-11 Thread yang sheng
Hi
I am using openstack liberty with ceph jewel.

All the glance images and cinder volumes are stored in ceph pools (images
and volumes pools)

I have some volumes in the ceph volumes pool but not registered in cinder
(database).

Is there anyway I can manually register these volumes (in ceph volumes
pool) in the cinder?

thanks
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] SRIOV and BOND

2016-07-11 Thread Brent Troge
Thanks for your response. In the meantime, I created an additional
throw-away subnet(192.168/16) on each network. So on the 'main' neutron
port, I call the 'production' subnet.
On the other neutron port(s) in the bond group, I call the "throw-away"
subnet.
So now only one IP is allocated out of my production subnet, and the other
allocations from the 'throw-away' subnets are just ignored. Since the
bond/members take on the
IP/MAC of the 'proudction' neutron port.





On Mon, Jul 11, 2016 at 12:48 AM, Sam Stoelinga 
wrote:

> If you're using PCI passhtrough with direct passthrough you shouldn't be
> hit by ARP spoofing protection so even though it assigns an IP you could in
> theory use any IP. If you need to allow a single IP to be allowed on
> multiple ports you can use allowed address pairs functionality. From what I
> understand you want to make sure it only assigns a single IP such that you
> aren't wasting an IP allocation?
>
> Looking at the Neutron API specs
>  it
> looks like only providing a network id and not a subnetid should work, but
> it still assigns an IP automatically.
> Using the CLI I tried to create a Neutron port without an IP but wasn't
> successful either. It seems to always assign an IP. For reference:
> neutron --debug port-create e33d8ee8-92e1-48e4-be5e-91573e731e27 --name
> test_net_only
> curl -g -i -X POST http://192.168.0.13:9696/v2.0/ports.json
> '{"port": {"network_id": "e33d8ee8-92e1-48e4-be5e-91573e731e27", "name":
> "test_net_only", "admin_state_up": true}}'
> RESP BODY: {"port": {"status": "DOWN", "binding:host_id": "",
> "allowed_address_pairs": [], "dns_assignment": [{"hostname":
> "host-192-168-111-12", "ip_address": "192.168.111.12", "fqdn":
> "host-192-168-111-12.openstacklocal."}], "device_owner": "",
> "binding:profile": {}, "port_security_enabled": true, "fixed_ips":
> [{"subnet_id": "fee4c6f2-d67e-43d5-b8a1-0f64c8775a39", "ip_address":
> "192.168.111.12"}], "id": "17926156-e7f8-4c00-bab8-8990d7df937c",
> "security_groups": ["62a33f63-bfae-4bd9-8662-507136d7598b"], "device_id":
> "", "name": "test_net_only", "admin_state_up": true, "network_id":
> "e33d8ee8-92e1-48e4-be5e-91573e731e27", "dns_name": "",
> "binding:vif_details": {}, "binding:vnic_type": "normal",
> "binding:vif_type": "unbound", "tenant_id":
> "4a79550e40794812b070db605728f734", "mac_address": "fa:16:3e:e8:2d:70"}}
>
> Maybe somebody else knows how to create a port without assigning a subnet
> / fixed IP address.
>
>
> On Fri, Jul 8, 2016 at 9:45 PM, Brent Troge 
> wrote:
>
>> I want to create a bond within my guest VM and trying to understand how
>> to
>> create my neutron ports without allocating an IP for each VF created.
>> I just need one IP allocated instead of each VF(neutron port) being
>> allocated an IP.
>>
>> I do not see anything within the neutron port api which supports
>> something like: 'no-ip-allocation;
>>
>> I am expecting something like the below.. See my made up property under
>> 'sriov_port2'
>>
>> resources:
>>   sriov_port1:
>> type: OS::Neutron::Port
>> properties:
>>   network: { get_param: my_net }
>>   vnic_type: direct
>>   sriov_port2:
>> type: OS::Neutron::Port
>> properties:
>>   network: { get_param: my_net }
>>   vnic_type: direct
>>   fixed-ip: false
>>
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] automatic role assignment

2016-07-11 Thread Boris Bobrov
On Monday 11 July 2016 09:25:43 Ivan Derbenev wrote:
> Hello!
> We are using OS liberty + Ubuntu LTS.
> I configured keystone to use ldap as an identity backend and sql as an
> assignment backend. Is there an automatic built-in way to assign some roles
> to all people from specific LDAP group?
> 
> 
> Regards,
> IT engineer
> Farheap, Russia
> Ivan Derbenev

Assign role to group. Do "openstack role add" and it will print available 
arguments, one of them will be --group.

-- 
Regards,
Boris

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


[Openstack] automatic role assignment

2016-07-11 Thread Ivan Derbenev
Hello!
We are using OS liberty + Ubuntu LTS.
I configured keystone to use ldap as an identity backend and sql as an 
assignment backend.
Is there an automatic built-in way to assign some roles to all people from 
specific LDAP group?


Regards,
IT engineer
Farheap, Russia
Ivan Derbenev

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack