Re: [Openstack] how to forbid the instances communicating on the same host but different bridges and vlans?

2012-06-02 Thread Vishvananda Ishaya
You could tell dnsmasq to use your router as the gateway instead of the network 
host and then not allow routing across vlans.

To use an external gateway use a config option like the following:
dnsmasq_config_file=/path/to/config

in that config file you can use:
dhcp_option=3,ip of router to force vms to use your router as their gateway.

Vish

On Jun 1, 2012, at 10:30 PM, romizhang1968 wrote:

 Vish,
 
 Thanks for your replay.
 Yes,I allowed icmp ping from 0.0.0.0/0, but the question is , i think the 
 different instance in different tenant and vlan on the same compute node 
 should not touch each other, admin03(192.168.2.3) in VLAN 200 and 201 should 
 only could get ip touch to the same tenant instance, should not can touch 
 aipu01(192.168.3.3) in VLAN 300 and aipuTenant even on the same compute node.
 I check the route table, openstack creates route item to each bridge on the 
 node, but in admin03,the route table only shows about how to go 192.168.2.0 
 and 192.168.21.0, have no way to touch the net of 192.168.3.0. but in 
 admin03,it could ping aipu01, that means it use the node route table, i did 
 not know why.
 so I want to know is there a way in openstack command to stop this situation, 
 not replay me to delete the compute node route item. and I think, each VM 
 should connect to the access port and go through trunk port(eth1 or eth2) 
 to communicate with others.
 here is my wants. 
 regards,
 Romi
 
 
 
 At 2012-06-02 00:47:49,Vishvananda Ishaya vishvana...@gmail.com wrote:
 Broadcast traffic should be blocked via the vlan separation and direct 
 traffic should be blocked via security groups. Do you have a security group 
 that allows ping traffic from 0.0.0.0/0?
 
 Vish
 
 On Jun 1, 2012, at 1:38 AM, romi zhang wrote:
 
 Hi,
  
 I use following command to create 2 NICs for the instances of adminTenant 
 and 1 NICs for aipuTenant:
  
 nova-manage network create --label=admin_web --fixed_range_v4=192.168.2.0/28 
 --num_networks=1 --vlan=200 --bridge=br200 --bridge_interface=eth1 
 --network_size=16 --multi_host=T 
 --project_id=5f9281bca6854fe3974a457d81afd78c
  
 nova-manage network create --label=admin_ssl 
 --fixed_range_v4=192.168.21.0/28 --num_networks=1 --vlan=201 --bridge=br201 
 --bridge_interface=eth2 --network_size=16 --multi_host=T 
 --project_id=5f9281bca6854fe3974a457d81afd78c
  
 nova-manage network create --label=aipu_web --fixed_range_v4=192.168.3.0/28 
 --num_networks=1 --vlan=300 --bridge=br300 --bridge_interface=eth1 
 --network_size=16 --multi_host=T 
 --project_id=ee29f5730caa40958bf4812a0fbec3d9
  
 But the result is:
 1.   the instance of admin03(192.168.2.3 192.168.21.3,belong 
 adminTenant) could successfully ping aipu01(192.168.3.3,belong aipuTenant) 
 on the same compute node(NC01,network+compute service) .
 2.   Of course,admin03 could not ping successfully aipu03(192.168.3.6) 
 on the another compute node(NC02,network+compute service).
  
 Is there a way or setting to forbid the IP touching between the instances of 
 different tenant in different bridges and VLANs on the same compute node?
  
 Romi
  
 ___
 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!!!

2012-06-02 Thread Từ Minh Mẫn
When I try to do tenant-create I also have problem:

No handlers could be found for logger keystoneclient.client
Unable to communicate with identity service: [Error 111] Connection
refused. (HTTP 400)

When I use command: keystone tenant-list, it have them same error!

Please help me!!!
Thanks so much!

On 1 June 2012 00:40, Dolph Mathews dolph.math...@gmail.com wrote:

 That's just a warning you can safely ignore for now (and a known issue):
 https://bugs.launchpad.net/keystone/+bug/936404

 On Thu, May 31, 2012 at 12:09 PM, Từ Minh Mẫn tuminh...@gmail.com wrote:

 Dear all,
 When I Create Tenants: I use command: keystone tenant-create --name admin,
 Have error: No handlers could be found for logger
 keystoneclient.client
 Please help me!!!


 On 29 May 2012 08:30, Từ Minh Mẫn tuminh...@gmail.com wrote:

 If I use Ubuntu 12.04 32bit, do I have any problem when I install cloud
 computing?


 On 29 May 2012 00:38, Sébastien Han han.sebast...@gmail.com wrote:

 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=serverbits=32release=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 tuminh...@gmail.comwrote:

 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 razique.mahr...@gmail.comwrote:

 Yes sorry,
 my question was intended to Từ Minh Mẫn tuminh...@gmail.com :-)


   Michael Pittaro mik...@lahondaresearch.org
  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 mik...@lahondaresearch.org
  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 razique.mahr...@gmail.com
  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 tuminh...@gmail.com
  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





 --
--

   Man Tu Minh
 Mobile   : 0989998815

 Email : tuminh...@gmail.com tuminh...@yahoo.com.vn




 --
--

   Man Tu Minh
 Mobile   : 0989998815

 Email : tuminh...@gmail.com tuminh...@yahoo.com.vn

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : 

Re: [Openstack] Volume creation stuck at status Creating

2012-06-02 Thread Sebastien HAN
Hi,

Does the libvirt logs show something? 

On 31 mai 2012, at 16:27, John Griffith john.griff...@solidfire.com wrote:

 
 
 On Thu, May 31, 2012 at 5:58 AM, Alisson Soares Limeira Pontes 
 apon...@cpqd.com.br wrote:
 Something changed in the nova-volume ubuntu packages instalation.
 I'd never had problems with nova-volume, but in my last two setups i cannot 
 attach volume and vm. Logs do not show any problem, so no clue why this 
 problem.
 
 
 2012/5/31 Milind milindkpa...@gmail.com
 Thanks,
 
 Any one know what is the problem or it is another bug?
 
 REgards,
 Milind
 
 On Thu, May 31, 2012 at 12:22 PM, William Herry 
 william.herry.ch...@gmail.com wrote:
 I can't tell what's wrong about your config, let others help you
 
 On Thu, May 31, 2012 at 2:50 PM, Milind milindkpa...@gmail.com wrote:
 Hi Just ran command... here is the output...
 
 root@ucmaster:/var/log/upstart# nova --debug  volume-create  
 --display_name=novavol5 --display_description=volumenova5 1
 connect: (ucmaster, 5000)
 send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: ucmaster:5000\r\nContent-Length: 
 117\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: openstackDemo, 
 passwordCredentials: {username: adminUser, password: secretword}}}'
 reply: 'HTTP/1.1 200 OK\r\n'
 header: Content-Type: application/json
 header: Vary: X-Auth-Token
 header: Date: Thu, 31 May 2012 06:42:50 GMT
 header: Transfer-Encoding: chunked
 connect: (ucmaster, 8776)
 send: u'POST /v1/68124ec3a778447093eba446aa896105/volumes HTTP/1.1\r\nHost: 
 ucmaster:8776\r\nContent-Length: 131\r\nx-auth-project-id: 
 openstackDemo\r\naccept-encoding: gzip, deflate\r\naccept: 
 application/json\r\nx-auth-token: 
 b0b433d2506145d0b4f5ab8e1fcb6478\r\nuser-agent: 
 python-novaclient\r\ncontent-type: application/json\r\n\r\n{volume: 
 {snapshot_id: null, display_name: novavol5, volume_type: null, 
 display_description: volumenova5, size: 1}}'
 reply: 'HTTP/1.1 200 OK\r\n'
 header: X-Compute-Request-Id: req-58d480c3-f729-4670-8c86-74ef9991993a
 header: Content-Type: application/json
 header: Content-Length: 274
 header: Date: Thu, 31 May 2012 06:42:50 GMT
 root@ucmaster:/var/log/upstart# clear
 
 
 
 
 
 
 On Thu, May 31, 2012 at 12:12 PM, Milind milindkpa...@gmail.com wrote:
 
 
 
 On Thu, May 31, 2012 at 12:08 PM, William Herry 
 william.herry.ch...@gmail.com wrote:
 I can't see any unusual log
 
 try:
 
  nova --debug volume-create --display_name=novavol4 
 --display_description=volumenova4 1 
 
 
 On Thu, May 31, 2012 at 2:33 PM, Milind milindkpa...@gmail.com wrote:
 I did that and issued following command.
 
 nova volume-create --display_name=novavol4 --display_description=volumenova4 1
 
 I have attached relevant part of log.
 
 Regards,
 Milind
 
 
 On Thu, May 31, 2012 at 11:48 AM, William Herry 
 william.herry.ch...@gmail.com wrote:
 add debug=true to /etc/nova/nova.conf and restart service(nova-volume I think)
 
 On Thu, May 31, 2012 at 2:16 PM, Milind milindkpa...@gmail.com wrote:
 In which config file?
 
 
 On Thu, May 31, 2012 at 11:43 AM, William Herry 
 william.herry.ch...@gmail.com wrote:
 have you add debug=true to config file
 
 On Thu, May 31, 2012 at 2:11 PM, Milind milindkpa...@gmail.com wrote:
 There is nothing in the logs :(
 
 
 
 On Thu, May 31, 2012 at 11:37 AM, William Herry 
 william.herry.ch...@gmail.com wrote:
 you should check logs to see what's going on
 
 On Thu, May 31, 2012 at 1:50 PM, Milind milindkpa...@gmail.com wrote:
 Hi,
 
 I am not able to resolve this error quite frustrated :(, it gets stuck at 
 volume creation with status as Creating
 
 
 
 
 Regards,
 Milind
 -- 
 Alisson Pontes
 
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
 
 
 Hi Milind,
 
 Sorry if you've already answered this, but what sort of setup is this?  Are 
 you using Essex, or latest from Trunk?  Is this a devstack install or other?  
 This is something I've seen before as well and it had to do with issues in my 
 configuration for the scheduler.  Let me know a bit more about your setup if 
 you have a chance.  Perhaps I can try to recreate and have a closer look.
 
 Thanks,
 John
 ___
 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] shall openstack use Openfiler(iscsi target) as volume service?

2012-06-02 Thread romi zhang
Hi,

 

There is an question always trouble me ,shall openstack use Openfiler(iscsi
target) as volume service?

Openfiler is a free iscsi software base on centos use ietd to create iscsi
target that can run on a standalone computer.

I saw we can use volume_driver=nova.volume.driver.ISCSIDriver and
cooperating with such as following items to connect ISCSI:

 

# iscsi_helper=ietadm

# iscsi_ip_address=$my_ip

# iscsi_num_targets=100

# iscsi_port=3260

# iscsi_target_prefix=iqn.2010-10.org.openstack:

# num_iscsi_scan_tries=3

 

My question is I could not find the way to tell volume driver the username
and password to access Openfiler for creating lun.

So, does it mean openstack could not connect a independent iscsi target host
running tgtd or ietd, just like nexenta?

 

Regards,

Romi

 

 

___
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] Not able to delete a running instance

2012-06-02 Thread Massimo Canonico

Hi,
thanks for your reply.

On 06/01/2012 06:54 PM, Vishvananda Ishaya wrote:

it looks like you are running a very old version of openstack (perhaps 
diablo?), so it might be harder to figure out the problem.

I have installed openstack on my fedora 16 by using this howto:
https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova#Images
(is it an old version?)

Please check:

a) if your compute worker is still up and running

Yes, right now I have installed everything in the same machine

b) if there is an error message in the nova-api.log or the nova-compute.log

I have no idea what happened, but today I am able to remove the instance.

I did not change anything.

Thanks,
 M


Vish

On Jun 1, 2012, at 3:30 AM, Massimo Canonico wrote:


Hi,
I have a running instance and I'm not able to delete it. It is the tty img 
proposed here:
https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova#Images

Note that new instances of this image work (can start-up and shutting-down).

Now the problem is that I'm not able to delete it.
- several time euca-terminate-instance did not work without any error message

[mex@minicloud cred]$ euca-describe-instances
RESERVATION r-6xvr06s5  mex default
INSTANCEi-0004  ami-000310.0.0.310.0.0.3
running nova_key (mex, minicloud.di.unipmn.it)  0   m1.small
2012-05-30T13:21:27Znovaaki-0001ari-0002
[mex@minicloud cred]$ euca-terminate-instances i-0004
[mex@minicloud cred]$ euca-describe-instances
RESERVATION r-6xvr06s5  mex default
INSTANCEi-0004  ami-000310.0.0.310.0.0.3
running nova_key (mex, minicloud.di.unipmn.it)  0   m1.small
2012-05-30T13:21:27Znovaaki-0001ari-0002


- several time nova deleteid without success:

[mex@minicloud cred]$ nova list
++--++--+
| ID |   Name   | Status |   Networks   |
++--++--+
| 4  | Server 4 | ACTIVE | mex=10.0.0.3 |
++--++--+
[mex@minicloud cred]$ nova delete 4
[mex@minicloud cred]$ nova list
++--++--+
| ID |   Name   | Status |   Networks   |
++--++--+
| 4  | Server 4 | ACTIVE | mex=10.0.0.3 |
++--++--+

- reboot: right now, I have openstack installed/configured in one machine. I 
tried to reboot it and nothing has changed.

Any suggestion, please?

Massimo


___
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] Can't ping instances in remote node .

2012-06-02 Thread tiến bùi minh
Hi, all.

I have two nodes
installation.
Server1  runs  all the components of Nova, Glance,Keystone and Horizon
(OpenStack Dashboard). Server2 runs only nova-compute. 
I am using FlatDHCP
mode  with a single network interface per
node.

network config :
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
        address 10.2.70.106
        netmask 255.255.255.0
        network 10.2.70.0
        broadcast 10.2.70.255
        gateway 10.2.70.1
        dns-nameservers 10.3.10.151
auto br100
iface br100 inet static
        address 192.168.3.1
        netmask 255.255.255.0
        bridge_stp off   
        bridge_fd 0    

Alter I assigned
floating ip to instances , I can ping to instances which running on server 1
but  I do it with instances are running
on server 2.
 
 
My nova.conf :

root@cloudca3:/home/cloudca3#
clear
root@cloudca3:/home/cloudca3#
cat /etc/nova/nova.conf 
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/run/lock/nova
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--s3_host=10.2.70.106
--ec2_host=10.2.70.106
--rabbit_host=10.2.70.106
--cc_host=10.2.70.106
--nova_url=http://10.2.70.106:8774/v1.1/
--routing_source_ip=10.2.70.106
--glance_api_servers=10.2.70.106:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.4
--sql_connection=mysql://novadbadmin:passwordcloud@127.0.0.1/nova
--ec2_url=http://10.2.70.106:8773/services/Cloud
--keystone_ec2_url=http://10.2.70.106:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--libvirt_type=kvm
--libvirt_use_virtio_for_bridges=true
--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
# vnc specific
configuration
--novnc_enabled=true
--novncproxy_base_url=http://10.2.70.106:6080/vnc_auto.html
--vncserver_proxyclient_address=10.2.70.106
--vncserver_listen=10.2.70.106
# network specific
settings
--network_manager=nova.network.manager.FlatDHCPManager
--public_interface=br100
--flat_interface=eth0
--flat_network_bridge=br100
--fixed_range=192.168.4.1/27
#--floating_range=10.2.70.106/27
--network_size=32
--flat_network_dhcp_start=192.168.4.33
--flat_injected=False
--force_dhcp_release
--iscsi_helper=tgtadm
--connection_type=libvirt
--root_helper=sudo
nova-rootwrap
--verbose
 
Check with ip addr  command :
 
3: virbr0:
NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc noqueue state DOWN 
    link/ether 4e:08:87:24:c5:78 brd
ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255
scope global virbr0
5: br100:
BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP 
    link/ether 50:e5:49:14:d6:f9 brd
ff:ff:ff:ff:ff:ff
    inet 192.168.4.33/27 brd 192.168.4.63 scope
global br100
    inet 192.168.3.1/24 brd 192.168.3.255 scope
global br100
    inet 10.2.70.106/24 brd 10.2.70.255 scope
global br100
    inet 10.2.70.129/32 scope global br100
    inet 10.2.70.130/32 scope global br100
    inet 10.2.70.131/32 scope global br100
    inet6 fe80::4ca2:a8ff:fe57:a569/64 scope
link 
   valid_lft forever preferred_lft forever

 

Nat rule :
Chain
nova-network-PREROUTING (1 references)
 pkts bytes target prot opt in out source   
destination 
    0 0 DNAT   tcp  --  *  *   0.0.0.0/0    
169.254.169.254  tcp dpt:80
to:10.2.70.106:8775
 3363  279K DNAT   all  --  *  *   0.0.0.0/0    
10.2.70.129  to:192.168.4.34
    5   240 DNAT   all  --  *  *   0.0.0.0/0    
10.2.70.130  to:192.168.4.41
    0 0 DNAT   all  --  *  *   0.0.0.0/0    
10.2.70.131  to:192.168.4.40
 
 
Chain
nova-network-float-snat (1 references)
 pkts bytes target prot opt in out source   
destination 
   11   660 SNAT   all  --  *  *   192.168.4.34 
0.0.0.0/0    to:10.2.70.129
    2   120 SNAT   all  --  *  *   192.168.4.41 
0.0.0.0/0    to:10.2.70.130
    5   300 SNAT   all  --  *  *   192.168.4.40 
0.0.0.0/0    to:10.2.70.131
Chain
nova-network-OUTPUT (1 references)
 pkts bytes target prot opt in out source   
destination 
   17  1020 DNAT   all  --  *  *   0.0.0.0/0    
10.2.70.129  to:192.168.4.34
    0 0 DNAT   all  --  *  *   0.0.0.0/0    
10.2.70.130  to:192.168.4.41
    0 0 DNAT   all  --  *  *   0.0.0.0/0    
10.2.70.131  to:192.168.4.40___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Quantum+Openvswitch: possible network configurations

2012-06-02 Thread Igor Laskovy
Hello all from sunny Kiev!

I have lab with two nodes (controller and compute) and
Quantum+Openvswitch setup.
With which options in nova.conf I can configure just simply putting my
instances into one network without providing any gw/nats, without
setting any ip subnets and dhcp activities for this network?
Just putting virtual nics in the bridge, mark it with some vlan
id/xvlan label and run traffic away through one of the network card of
physical host.

-- 
Igor Laskovy
Kiev, Ukraine

___
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!!!

2012-06-02 Thread Dolph Mathews
Can you share your keystone configuration and keystoneclient configuration? A 
400 could be as simple as the keystone service not running.

-Dolph Mathews

On Jun 2, 2012, at 1:48 AM, Từ Minh Mẫn tuminh...@gmail.com wrote:

 When I try to do tenant-create I also have problem:
 
 No handlers could be found for logger keystoneclient.client
 Unable to communicate with identity service: [Error 111] Connection refused. 
 (HTTP 400)
 
 When I use command: keystone tenant-list, it have them same error!
 
 Please help me!!!
 Thanks so much!
 
 On 1 June 2012 00:40, Dolph Mathews dolph.math...@gmail.com wrote:
 That's just a warning you can safely ignore for now (and a known issue): 
 https://bugs.launchpad.net/keystone/+bug/936404
 
 On Thu, May 31, 2012 at 12:09 PM, Từ Minh Mẫn tuminh...@gmail.com wrote:
 Dear all, 
 When I Create Tenants: I use command: keystone tenant-create --name admin,
 Have error: No handlers could be found for logger keystoneclient.client
 Please help me!!!
 
 
 On 29 May 2012 08:30, Từ Minh Mẫn tuminh...@gmail.com wrote:
 If I use Ubuntu 12.04 32bit, do I have any problem when I install cloud 
 computing?
 
 
 On 29 May 2012 00:38, Sébastien Han han.sebast...@gmail.com wrote:
 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=serverbits=32release=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 tuminh...@gmail.com 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 razique.mahr...@gmail.com 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
 
 
 
 
 
 -- 
--
 
   Man Tu Minh
 Mobile   : 0989998815
 
 Email : tuminh...@gmail.com tuminh...@yahoo.com.vn
 
 
 
 -- 
--
 
   Man Tu Minh
 Mobile   : 

Re: [Openstack] [metering] nova volume notifications

2012-06-02 Thread Craig Vyvial
Tomasz,

There are volume notifications being sent by the volume manger now in
trunk. This is not in the Essex release. Here is a list of all
the notifications that are currently being emitted by the managers.

http://wiki.openstack.org/SystemUsageData

Hope this helps.

Thanks,
-Craig

On Fri, Jun 1, 2012 at 1:02 PM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:

 The service that manages the volumes should send notifications. If it
 doesn't do so already, we will need to update it.


 On Fri, Jun 1, 2012 at 9:49 AM, Tomasz Paszkowski ss7...@gmail.comwrote:

 Hi,

 Does anyone have any idea how to implement metering of nova volumes
 creation/termination ? As for instances we have notifications topic.
 But I can't find anything similar for volumes. My first idea
 was to track volume creation messages but I'am afraid that attaching
 another consumer to volume_topic will break messages from being
 delivered to proper recipient.



 --
 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


___
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] [metering] nova volume notifications

2012-06-02 Thread Tomasz Paszkowski
Great, many thanks. I'am still using essex as development base, it's
time to change.

,
On Sat, Jun 2, 2012 at 6:11 PM, Craig Vyvial cp16...@gmail.com wrote:
 Tomasz,

 There are volume notifications being sent by the volume manger now in trunk.
 This is not in the Essex release. Here is a list of all
 the notifications that are currently being emitted by the managers.

 http://wiki.openstack.org/SystemUsageData

 Hope this helps.

 Thanks,
 -Craig

 On Fri, Jun 1, 2012 at 1:02 PM, Doug Hellmann doug.hellm...@dreamhost.com
 wrote:

 The service that manages the volumes should send notifications. If it
 doesn't do so already, we will need to update it.


 On Fri, Jun 1, 2012 at 9:49 AM, Tomasz Paszkowski ss7...@gmail.com
 wrote:

 Hi,

 Does anyone have any idea how to implement metering of nova volumes
 creation/termination ? As for instances we have notifications topic.
 But I can't find anything similar for volumes. My first idea
 was to track volume creation messages but I'am afraid that attaching
 another consumer to volume_topic will break messages from being
 delivered to proper recipient.



 --
 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





-- 
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


Re: [Openstack] Quantum+Openvswitch: could not open /dev/net/tun: Operation not permitted

2012-06-02 Thread Igor Laskovy
Guys, I really confused about this.

I have recreated nova.conf for a little another design, but issue
could not configure  /dev/net/tun: Operation not permitted during
resuming instances is still present!
I need just to clarify, that this happening if I will reboot/halt host
after suspending instances.

Awaiting any advice!

On Sun, May 27, 2012 at 1:00 PM, Igor Laskovy igor.lask...@gmail.com wrote:
 Back according to main subject about /dev/net/tun I still have another
 but similar issue.
 Yesterday I have suspend my instances and shutdown lab.
 Today, when I try nova resume for them I have the following in
 /var/log/nova/nova-compute.log:

 2012-05-27 05:30:01 TRACE nova.rpc.amqp libvirtError: internal error
 Process exited while reading console log output: char device
 redirected to /dev/pts/4
 2012-05-27 05:30:01 TRACE nova.rpc.amqp kvm: -netdev
 tap,ifname=tap4362ce16-32,script=,id=hostnet0: could not configure
 /dev/net/tun (tap4362ce16-32): Operation not permitted
 2012-05-27 05:30:01 TRACE nova.rpc.amqp kvm: -netdev
 tap,ifname=tap4362ce16-32,script=,id=hostnet0: Device 'tap' could not
 be initialized

 On Sat, May 26, 2012 at 11:40 PM, Dan Wendlandt d...@nicira.com wrote:
 Hi Igor,

 I'd first access the VM via VNC and make sure it has booted and is getting
 an IP address via DHCP.  The easiest way to do this is using the VNC
 consoles exposed via Horizon, but you can also use a tool like vncviewer
 directly from the command line.

 If you think it may be an issue with security groups, running nova with the
 following flag will disable security groups so you can see if that is what
 is blocking the
 traffic: firewall_driver=nova.virt.firewall.NoopFirewallDriver .  Of course,
 you'll need to restart nova-compute.  With devstack, you can set this in
 your localrc: LIBVIRT_FIREWALL_DRIVER=nova.virt.firewall.NoopFirewallDriver
 .

 Dan


 On Sat, May 26, 2012 at 11:31 AM, Igor Laskovy igor.lask...@gmail.com
 wrote:

 Thank you Dan, Chris, Dean and Soheil for help. I very appreciated your
 help!

 Yes, I using Precise for this lab and after I have added /dev/net/tun
 to the cgroup_device_acl list I have ACTIVE state for my running
 instances. BTW, the doc
 http://openvswitch.org/openstack/documentation/ already have this
 clarification, thanks))

 Well, although that the instances are running, I can't ping or ssh to
 them.
 I already doing this:
 $ nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0
 $ nova secgroup-add-rule default tcp 22 22 0.0.0.0/0
 but didn't help!

 On Fri, May 25, 2012 at 12:40 AM, Dan Wendlandt d...@nicira.com wrote:
  Hi Igor,
 
  Are you running this on Precise?  If so, Precise is a bit pickier than
  previous versions about requiring a setting in /etc/libvirt/qemu.conf
 
  You need to add /dev/net/tun to the cgroup_device_acl list in that file,
  and
  restart libvirt.
 
  This is actually handled automatically by a branch I've pushed for
  review in
  devstack: https://review.openstack.org/#/c/7001/
 
  It has lots of positive reviews, but still needs one more core review
  and
  I've been waiting a while.  If you're a devstack core, please give me a
  hand! :)
 
  Dan
 
  p.s.  the root cause of needing to tweak /etc/libvirt/qemu.conf is that
  we're using libvirt interface type=ethernet elements to work with
  openvswitch.  Starting in libvirt 0.9.11 (not available in precise),
  openvswitch is integrated directly with libvirt, meaning that using
  type=ethernet (and the workaround) is no longer necessary.
 
 
  On Thu, May 24, 2012 at 1:05 PM, Igor Laskovy igor.lask...@gmail.com
  wrote:
 
  Hello all from sunny Kiev))
 
  I have built nova+quantum+openvswitch without nova-volume lab on two
  nodes - one controller with everything on it except nova-compute and
  second dedicated compute node with nova-compute:
 
  During creating VM I have error which I still can't fix:
  $ nova boot --image precise --flavor m1.tiny  my-precise-vm3
  $ nova list
 
 
  +--+++--+
  |                  ID                  |      Name      | Status |
  Networks |
 
 
  +--+++--+
  | 5a72aa9f-5743-486a-9496-130d367bc665 | my-precise-vm3 | ERROR  |
   |
 
 
  +--+++--+
 
  # cat /var/log/libvirt/qemu/instance-0012.log
  2012-05-24 19:51:47.994+: starting up
  LC_ALL=C
  PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
  QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 512 -smp
  1,sockets=1,cores=1,threads=1 -name instance-0012 -uuid
  5a72aa9f-5743-486a-9496-130d367bc665 -nodefconfig -nodefaults -chardev
 
 
  socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0012.monitor,server,nowait
  -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
  -no-shutdown -drive
 
 
  

Re: [Openstack] install cloud computing by openstack!!!

2012-06-02 Thread Từ Minh Mẫn
Sorry,
I check step by step from create database, and when I use command: sudo
keystone-manage db_sync
It have a error: 2003,Can't connect to MySQL server on
'10.10.10.2 (101)) None None

Please help me: Can I check this error?
Thanks so much!

On 2 June 2012 23:08, Dolph Mathews dolph.math...@gmail.com wrote:

 Can you share your keystone configuration and keystoneclient
 configuration? A 400 could be as simple as the keystone service not running.

 -Dolph Mathews

 On Jun 2, 2012, at 1:48 AM, Từ Minh Mẫn tuminh...@gmail.com wrote:

 When I try to do tenant-create I also have problem:

 No handlers could be found for logger keystoneclient.client
 Unable to communicate with identity service: [Error 111] Connection
 refused. (HTTP 400)

 When I use command: keystone tenant-list, it have them same error!

 Please help me!!!
 Thanks so much!

 On 1 June 2012 00:40, Dolph Mathews dolph.math...@gmail.com wrote:

 That's just a warning you can safely ignore for now (and a known issue):
 https://bugs.launchpad.net/keystone/+bug/936404

 On Thu, May 31, 2012 at 12:09 PM, Từ Minh Mẫn tuminh...@gmail.comwrote:

 Dear all,
 When I Create Tenants: I use command: keystone tenant-create --name
 admin,
 Have error: No handlers could be found for logger
 keystoneclient.client
 Please help me!!!


 On 29 May 2012 08:30, Từ Minh Mẫn tuminh...@gmail.com wrote:

 If I use Ubuntu 12.04 32bit, do I have any problem when I install cloud
 computing?


 On 29 May 2012 00:38, Sébastien Han han.sebast...@gmail.com wrote:

 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=serverbits=32release=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 tuminh...@gmail.comwrote:

 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 razique.mahr...@gmail.comwrote:

 Yes sorry,
 my question was intended to Từ Minh Mẫn tuminh...@gmail.com :-)


   Michael Pittaro mik...@lahondaresearch.org
  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 mik...@lahondaresearch.org
  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 razique.mahr...@gmail.com
  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 tuminh...@gmail.com
  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   : 

Re: [Openstack] [Netstack] question on get_network_details api call

2012-06-02 Thread Dan Wendlandt
Hi Irena, Bob, Salvatore,

Just catching up the thread, and looping the netstack and openstack lists
in as well, as this info is general useful in my opinion.

Our model with Quantum, like Nova, is that it is definitely ok to extend
the content of a core object with additional attributes.  These attributes
should be formatted properly as extended attribute, so that the key of
the attribute is extension-alias:attribute-name

This is done pretty commonly within Nova.  Two simple examples are:
- nova/api/openstack/compute/contrib/scheduler_hints.py
- nova/api/openstack/compute/contrib/extended_status.py

I do not believe you need to (or should) modify the view-builder code for
the core object when you want to add an extended attribute to it.  Instead,
the extension framework has you write a wsgi controller specific to the
extension that is inserted as its own stage into the wsgi request and
response processing pipeline.  Thus, when the request is passed in, your
code gets a chance to parse the data, and the the response is passed back,
your code gets a chance to add data to it.

Using the Nova code as example is probably the best bet if you can find a
good example within quantum.  Quantum's extension framework (and several
other openstack projects) all use essentially the same model.

Dan


On Sat, Jun 2, 2012 at 8:43 AM, Robert Kukura rkuk...@redhat.com wrote:

 On 06/02/2012 05:02 AM, Irena Berezovsky wrote:
  Hi,
  Bob, Dan,
  I ran into following wiki page:
 
 http://wiki.openstack.org/QuantumAPIExtensionsaction=AttachFiledo=viewtarget=quantum_api_extension.pdf
  'port profile' is exactly what I was looking for to expose in the plugin.
  I would like to add the port profile retrieval capability and contribute
 the implementation.
 
  Can you please advise if there is any disagreement on getting it into
 core API? Shall I do it via extension?
  Bob, seems that you are dealing with similar issues.
  What do you suggest?
 
  Thanks a lot,
  Irena

 Irena,

 I'm not sure there is any consensus around using a network profile for
 this. I did see that document as well as archived discussion about
 defining port profile and network profile as extensible collections
 of attributes. But the existing port profile extension looks to be
 Cisco-specific, and seems to serve a somewhat different purpose.

 My current thinking is that we'd be better off long term following the
 lead of Nova and other projects in supporting extension data within
 the existing resources instead of requiring introduction of a new
 resource just to hold plugin-specific attributes.

 But, in the short term, it might make the most sense for each extension
 just to provide its own resource extension with its attributes. That's
 what I'm tentatively planning to do for the provider-network blueprint,
 but would reconsider if there was consensus that either the extension
 data support or a more general network profile should be added now.

 -Bob




-- 
~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Netstack] question on get_network_details api call

2012-06-02 Thread Irena Berezovsky
Dan, thank you very much for pointing to nova examples.
Following these examples and also 
http://wiki.openstack.org/WritingRequestExtensions guidelines I understand how 
to add extension to nova, but still has questions how to add it to Quantum.
Nova extensions make use of nova.api.openstack.extensions module and Quantum 
has its own implementation.
Can you please point to some documentation regarding writing Quantum extensions?
Thanks a lot,
Irena

From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Saturday, June 02, 2012 8:57 PM
To: Robert Kukura
Cc: Irena Berezovsky; Salvatore Orlando; netst...@lists.launchpad.net; 
openstack@lists.launchpad.net
Subject: Re: [Netstack] question on get_network_details api call

Hi Irena, Bob, Salvatore,

Just catching up the thread, and looping the netstack and openstack lists in as 
well, as this info is general useful in my opinion.

Our model with Quantum, like Nova, is that it is definitely ok to extend the 
content of a core object with additional attributes.  These attributes should 
be formatted properly as extended attribute, so that the key of the attribute 
is extension-alias:attribute-name

This is done pretty commonly within Nova.  Two simple examples are:
- nova/api/openstack/compute/contrib/scheduler_hints.py
- nova/api/openstack/compute/contrib/extended_status.py

I do not believe you need to (or should) modify the view-builder code for the 
core object when you want to add an extended attribute to it.  Instead, the 
extension framework has you write a wsgi controller specific to the extension 
that is inserted as its own stage into the wsgi request and response processing 
pipeline.  Thus, when the request is passed in, your code gets a chance to 
parse the data, and the the response is passed back, your code gets a chance to 
add data to it.

Using the Nova code as example is probably the best bet if you can find a good 
example within quantum.  Quantum's extension framework (and several other 
openstack projects) all use essentially the same model.

Dan


On Sat, Jun 2, 2012 at 8:43 AM, Robert Kukura 
rkuk...@redhat.commailto:rkuk...@redhat.com wrote:
On 06/02/2012 05:02 AM, Irena Berezovsky wrote:
 Hi,
 Bob, Dan,
 I ran into following wiki page:
 http://wiki.openstack.org/QuantumAPIExtensionsaction=AttachFiledo=viewtarget=quantum_api_extension.pdf
 'port profile' is exactly what I was looking for to expose in the plugin.
 I would like to add the port profile retrieval capability and contribute the 
 implementation.

 Can you please advise if there is any disagreement on getting it into core 
 API? Shall I do it via extension?
 Bob, seems that you are dealing with similar issues.
 What do you suggest?

 Thanks a lot,
 Irena
Irena,

I'm not sure there is any consensus around using a network profile for
this. I did see that document as well as archived discussion about
defining port profile and network profile as extensible collections
of attributes. But the existing port profile extension looks to be
Cisco-specific, and seems to serve a somewhat different purpose.

My current thinking is that we'd be better off long term following the
lead of Nova and other projects in supporting extension data within
the existing resources instead of requiring introduction of a new
resource just to hold plugin-specific attributes.

But, in the short term, it might make the most sense for each extension
just to provide its own resource extension with its attributes. That's
what I'm tentatively planning to do for the provider-network blueprint,
but would reconsider if there was consensus that either the extension
data support or a more general network profile should be added now.

-Bob



--
~~~
Dan Wendlandt
Nicira, Inc: www.nicira.comhttp://www.nicira.com
twitter: danwendlandt
~~~

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


Re: [Openstack] shall openstack use Openfiler(iscsi target) as volume service?

2012-06-02 Thread Vishvananda Ishaya
The default iscisi driver doesn't support CHAP. If you want to use chap 
credentials for iscsi, you will have to modify the existing driver or create a 
new one.

for example, check out:

nova/volume/san.py

You simply need to write the provider location field with the chap credentials 
into the database properly and nova will use it. Should be a fairly easy change 
to add custom chap credentials (perhaps even based on a flag)

Vish

On Jun 2, 2012, at 5:27 AM, romi zhang wrote:

 Hi,
  
 There is an question always trouble me ,shall openstack use Openfiler(iscsi 
 target) as volume service?
 Openfiler is a free iscsi software base on centos use ietd to create iscsi 
 target that can run on a standalone computer.
 I saw we can use volume_driver=nova.volume.driver.ISCSIDriver and 
 cooperating with such as following items to connect ISCSI:
  
 # iscsi_helper=ietadm
 # iscsi_ip_address=$my_ip
 # iscsi_num_targets=100
 # iscsi_port=3260
 # iscsi_target_prefix=iqn.2010-10.org.openstack:
 # num_iscsi_scan_tries=3
  
 My question is I could not find the way to tell volume driver the username 
 and password to access Openfiler for creating lun.
 So, does it mean openstack could not connect a independent iscsi target host 
 running tgtd or ietd, just like nexenta?
  
 Regards,
 Romi
  
  
 ___
 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