Re: [Openstack] Dashboard problem, bug or wrong version?

2011-10-06 Thread Rafael Durán Castañeda
Jae, tranks for your suggestion, but I don't think is a glance problem,
since server requests depends on openstackx (unless I 'm wrong).  Any other
suggestion about how to solve the problem?

El 6 de octubre de 2011 02:57, Jae Sang Lee hyan...@gmail.com escribió:

 Hi,

 In my case, I tried to reinstall glance with trunk version. I think glance
 was wrong maybe. Try reinstall glance latest version.



 2011/10/6 Rafael Durán Castañeda rafadurancastan...@gmail.com

 Hi,

 I'm trying to get a Keystone/Dashboard/Nova/Glance system (based on
 Diablo releases) without success. Dashboard points to endpoints/openstackx
 errors:

  Unable to get instance list: This error may be caused by a misconfigured
 nova url in keystone's service catalog, or by missing openstackx extensions
 in nova. See the dashboard README.

 From console I've tried:


 curl -G -H X-Auth-Token: 999888777666
 http://10.131.0.24:8774/v1.1/1/servers
 {servers: []}

 But Dashboard is trying:

 GET /v1.1/1/extras/servers?fresh=1317829720.03 HTTP/1.1
 Host: 10.131.0.24:8774
 x-auth-token: 0db0f991-124a-4899-9829-18eca20c7c24
 accept-encoding: gzip, deflate
 user-agent: python-openstack-compute/2.0a1


 HTTP/1.1 404 Not Found
 Content-Length: 52
 Content-Type: text/plain; charset=UTF-8
 Date: Wed, 05 Oct 2011 15:50:06 GMT

 404 Not Found

 The resource could not be found.

 So it isn't working due the  '/extras'  part on URI, so I think I might be
 using the wrong version of openstackx, right now I'm using Dahsboard
 pip-requires version:

 -e git+https://github.com/cloudbuilders/openstackx.git#egg=openstackx

 I've already tried change from master to Diablo branch, but not working
 yet. Any hint???



 ___
 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] user interface

2011-10-06 Thread Khaled Ben Bahri

Hi Tres,

Thanks for your help :)
I will try it 

Best regards
Khaled

Subject: Re: [Openstack] user interface
From: t...@treshenry.net
Date: Wed, 5 Oct 2011 12:00:29 -0400
CC: openstack@lists.launchpad.net
To: khaled-...@hotmail.com



Hi Khaled,
The OpenStack Dashboard includes basic support for Swift if you are looking for 
a simple web interface to manage containers and objects. Instructions for 
installing Dashboard and enabling Swift can be found at: 
http://wiki.openstack.org/OpenStackDashboard
Tres
On Oct 5, 2011, at 11:11 AM, Khaled Ben Bahri wrote:Hi all,

To manage files at swift I use swift tool commands (st)
I wonder if there are any graphical user interface or web interface for ubuntu 
system
I found cyberduck software for windows and MacOs, and it works fine.


thanks in advance for any help

Best regards
Khaled
___
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] Keystone Diablo Release

2011-10-06 Thread Fabrice Bacchella

Le 5 oct. 2011 à 21:51, Nick Owen a écrit :

 On 10/05/2011 03:19 PM, Fabrice Bacchella wrote:
 
 Le 5 oct. 2011 à 17:23, Ziad Sawalha a écrit :
 
 Good people at the OpenStack summit in Boston reminded me that I did not 
 announce the Keystone release that we tagged here: 
 https://github.com/openstack/keystone/tree/2011.3
 
 This is the Diablo release running the latest and final 2.0 API.
 
 We're discussing at the summit what to work on next. RBAC (authorization) 
 is in hot demand.
 
 Did you look at the integration with enterprise authentication like Active 
 Directory, Kerberos or SSO like CAS ?
 
 Radius would get you AD and all the two-factor authentication solutions.

But not the SSO provided by Kerberos or CAS.

Radius as far as I know manage authentication, but what about authorization ?

___
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] Introducing the OpenStack CDN As a Service project

2011-10-06 Thread Balle, Susanne
Hello Stackers!

Based on the great feedback from our Monday session here at the Openstack 
summit we have created an Openstack CDN As A Service project on launchpad.

The CDN Service is a framework to enable OpenStack services (storage and 
compute) to interact with a variety of CDN providers. It consists of a Service 
Layer APIs, a control fabric, and an extension mechanism to allow open or 
proprietary vendors of CDN services to plug in. Other use-cases such as Live 
streaming will also be considered.

https://launchpad.net/cndaas

The group will work towards the following goals:

1. Define a Service layer APIs
2. Understand how do we best integrate with the CDN providers
3. Define the origin server/end-point in a consistent way across all form of 
storages, compute, etc..
4. Define CDN public URI
5. Create an implementation of the Service.

We have a lot of work in front of us so if you are interested in contributing 
to this great project please join the CDN as a Service team:

https://launchpad.net/~cdnaas-core

Looking forward to hearing from you

Susanne Balle
___
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] Several keystone questions ...

2011-10-06 Thread Kuo Hugo
Hi folks ,

After several days work on keystone / python-novaclient / glance

There's some more questions want to discuss with everyone...

1. What's the difference of python-novaclient between
devstackhttps://github.com/cloudbuilders/python-novaclient
 and rackspace https://github.com/rackspace/python-novaclient , as I know
devstack's version forked from rackspace.. but while I install each of
them... only devstack's python-novaclient worked fine with
Keystonehttps://github.com/cloudbuilders/keystone .
Within rackspace version , always got Invalid OpenStack Nova Credentials
how come ??

2. For now , a keystone server is running . And it seems only support OSAPI
...am I right ?  I dig many docs only talk about adding NOVA OSAPI enpoint
templates , but no one talk about EC2 API(but EC2 features in source code).

3. We can using cloud with Dashbord smoothly for basic usage. So does
nova-client . I found that nova-client CLI tool could not
add-key-pair/show-keypair ...I think it's fine , just add it direct from API
endpoint .  But the problem is , nova boot can not assign key-pair while
fire up an instance.

4. The workflow between all services and keystone , plz correct me.
novaclient  keystone - nova -- keystone - novaclient
glance client - keystone -- glance --keystone --
glance client


Cheers
Hugo Kuo




-- 
+Hugo Kuo+
tonyt...@gmail.com
hugo@cloudena.com
+886-935-004-793

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


[Openstack] euca-authorize strange behaviour

2011-10-06 Thread Aleksandr Petrovich
Hi guys.
Recently, I've stumbled upon strange behaviour of euca-authorize
command. I'm using Diablo release
If I create two security groups and add a rule using  euca-authorize
command to authorize ICMP traffic from one group to another, why am I
not able to add another rule for, say, tcp traffic?
Here are the commands I've tried:

[apetrovich@ostcore-wslab2 ]$ euca-describe-groups
GROUP    project1    default    default
[apetrovich@ostcore-wslab2 ]$ euca-add-group -d mygroup description mygroup
GROUP    mygroup    mygroup description
[apetrovich@ostcore-wslab2 ]$ euca-describe-groups
GROUP    project1    default    default
GROUP    project1    mygroup    mygroup description
[apetrovich@ostcore-wslab2 ]$ euca-add-group -d another description mygroup2
GROUP    mygroup2    another description
[apetrovich@ostcore-wslab2 ]$ euca-describe-groups
GROUP    project1    default    default
GROUP    project1    mygroup    mygroup description
GROUP    project1    mygroup2    another description
[apetrovich@ostcore-wslab2 ]$ euca-authorize --protocol icmp -t -1:-1
--source-group mygroup mygroup2
mygroup2 mygroup None icmp -1 -1 0.0.0.0/0
GROUP    mygroup2
PERMISSION    mygroup2    ALLOWS    icmp    -1    -1    GRPNAME
mygroup    FROM    CIDR    0.0.0.0/0
[apetrovich@ostcore-wslab2 ]$ euca-authorize --protocol tcp
--port-range 22 --source-group mygroup mygroup2
mygroup2 mygroup None tcp 22 22 0.0.0.0/0
ApiError: {'to_port': 22, 'group_id': 2L, 'protocol': 'tcp',
'from_port': 22, 'parent_group_id': 3L} - This rule already exists in
group

This seems very strange, so I digged in to the sources and found that
this is happens because of  the method _security_group_rule_exists of
the nova.api.ec2.CloudController:

def _security_group_rule_exists(self, security_group, values):
    Indicates whether the specified rule values are already
   defined in the given security group.
    
    for rule in security_group.rules:
    if 'group_id' in values:
    if rule['group_id'] == values['group_id']:
    return rule['id']
    else:
    is_duplicate = True
    for key in ('cidr', 'from_port', 'to_port', 'protocol'):
    if rule[key] != values[key]:
    is_duplicate = False
    break
    if is_duplicate:
    return rule['id']
    return False

And it looks like it explicitly checks for the source group of the new
rule, and if there is already exists a rule with the same source group
it returns id of that group, so, it is not possible to add a different
rule with the same source group. Is it expected behaviour and I'm
missing something, or is it just a bug?

___
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] Xen image starts Kernel Panic in Diablo

2011-10-06 Thread Rogério Vinhal Nunes
I've got it working right now using FlatDHCPManager. :)
The problem with the tty's is that there's no tty configured to the instance
image, but I can access it quite fine with ssh, both the ttylinux and the
Ubuntu image. I may open a bug later to documentate the change I had to do
with libvirt.xml.template for it to work.

Just clear me out on this, why wouldn't FlatManager work injecting the fixed
IP? Is it fine to use FlatDHCPManager with just one interface? I have a
controller, two compute nodes and a gateway in a simple L2 network. The
controller bridge now seems to have 2 IPs because it responds both pings.

I'm still having some trouble with live migration, but I will do some more
research on it before and then, if I can't get it to work, I'll create
another topic regarding it.

Thanks for the help. :)

Em 5 de outubro de 2011 11:16, Rogério Vinhal Nunes
roge...@dcc.ufmg.brescreveu:

 It's not clear to me why should I be using DHCP. I've configured the system
 to use the simple FlatManager, shouldn't it inject the desired IP in the
 image when the instance spawns? Is there a DHCP running even if I don't use
 Vlan or FlatDHCP?

 I've actually used tcpdump to look for DHCP packages and found out that the
 instances are indeed sending broadcast requests and having no response.

 My system is a cloud controller with two compute nodes, shouldn't I be able
 to set it up with FlatManager? My configuration was generated by the
 nova-install script and I did some changes as I needed to make it work. My
 bridge is configured to xenbr0 in the database and also in the system.

 This is the controller nova.conf:

 --dhcpbridge_flagfile=/etc/nova/nova.conf
 --dhcpbridge=/usr/bin/nova-dhcpbridge
 --logdir=/var/log/nova
 --state_path=/var/lib/nova
 --lock_path=/var/lock/nova
 --verbose
 --s3_host=127.0.0.1
 --rabbit_host=10.0.254.6
 --cc_host=10.0.254.6
 --ec2_url=http://10.0.254.6:8773/services/Cloud
 --fixed_range=10.0.10.0/24
 --network_size=100
 --FAKE_subdomain=ec2
 --routing_source_ip=10.0.254.6
 --verbose
 --sql_connection=mysql://root:root@10.0.254.6/nova
 --network_manager=nova.network.manager.FlatManager
 --flat_network_bridge=xenbr0
 --glance_api_servers=10.0.254.6:9292
 --image_service=nova.image.glance.GlanceImageService

 And this is the compute nodes nova.conf:

 --dhcpbridge_flagfile=/etc/nova/nova.conf
 --dhcpbridge=/usr/bin/nova-dhcpbridge
 --logdir=/var/log/nova
 --state_path=/var/lib/nova
 --lock_path=/var/lock/nova
 --verbose
 --s3_host=10.0.254.6
 --rabbit_host=10.0.254.6
 --cc_host=10.0.254.6
 --ec2_url=http://10.0.254.6:8773/services/Cloud
 --sql_connection=mysql://root:root@10.0.254.6/nova
 --network_manager=nova.network.manager.FlatManager
 --flat_network_bridge=xenbr0
 --libvirt_type=xen
 --xenapi_remap_vbd_dev=true
 --glance_api_servers=10.0.254.6:9292
 --image_service=nova.image.glance.GlanceImageService
 --nouse_cow_images


 Thanks for the support, I may be a little more confused about the
 configuration than I thought.

 Em 4 de outubro de 2011 18:24, Vishvananda Ishaya 
 vishvana...@gmail.comescreveu:

 Yes that is the rule.  But that rule is not going to work if you don't
 receive an ip address via dhcp.  So you need to make sure the dhcp piece is
 working.  My guess is that once you get dhcp working, the metadata rule will
 work since it looks like it is being created correctly.

 Vish

 On Oct 4, 2011, at 12:38 PM, Rogério Vinhal Nunes wrote:

 I don't think the ubuntu image is expecting xvda anywhere. The disk is sda
 and after I've changed the libvirt.xml.template, so is root= option. The
 image is the ubuntu localimage mentioned in the documentation.

 I've tried to telnet 169.254.169.254 32 in the compute node and it
 didn't find anything while telnet 10.0.254.6 8773 does respond. This is
 the part of the iptables-save that messes with the routing of nova, did the
 Diablo configuration also change regarding to this?

 -A PREROUTING -j nova-compute-PREROUTING
 -A PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT
 --to-destination 10.0.254.6:8773
 -A POSTROUTING -j nova-compute-POSTROUTING

 I understand that it should forward anything destined to
 169.254.169.254/32 port 80 to 10.0.254.6:8773. But that isn't happening
 even with telnet. Does the nova-compute-PREROUTING rule have a part in this?
 The configuration I've done is just running iptables -A PREROUTING -d
 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination
 10.0.254.6:8773 .

 Em 4 de outubro de 2011 16:22, Vishvananda Ishaya 
 vishvana...@gmail.comescreveu:

 It looks like your dhcp is failing for some reason.  There are a number
 of things that could theoretically cause this.   You might start using
 tcpdump to find out if the dhcp request packet is coming out of the vm and
 if it is being responded to by dnsmasq on the nova-network host.  I'm not
 sure about the ubuntu image, is it expecting xvda there?

 On Oct 4, 2011, at 12:02 PM, Rogério Vinhal Nunes wrote:

 That pretty much 

Re: [Openstack] openstack-nova

2011-10-06 Thread Lorin Hochstein
Armaan:

This is already happening, see: 
https://github.com/openstack/nova/blob/master/nova/rpc/impl_kombu.py

Lorin
--
Lorin Hochstein, Computer Scientist
USC Information Sciences Institute
703.812.3710
http://www.east.isi.edu/~lorin




On Oct 6, 2011, at 7:18 AM, Armaan wrote:

 Hi,
 
 i am asking this question out curiosity, Nova uses Carrot to connect with 
 RabbitMQ environment.
 But Carrot has already been discontinued in favor of Kombu framework.
 So in near future, is there any possibility that nova will use Kombu instead 
 of carrot.
 
 
 Regards
 Syed Armani
 ___
 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] Several keystone questions ...

2011-10-06 Thread Anthony Young


 1. What's the difference of python-novaclient between 
 devstackhttps://github.com/cloudbuilders/python-novaclient
  and rackspace https://github.com/rackspace/python-novaclient , as I
 know devstack's version forked from rackspace.. but while I install each of
 them... only devstack's python-novaclient worked fine with 
 Keystonehttps://github.com/cloudbuilders/keystone .
 Within rackspace version , always got Invalid OpenStack Nova Credentials
 how come ??


In general, project branches referenced in devstack/master are either
release branches or slightly-lagging mirrors of trunk.

There was a recent change in python-novaclient where it now expects
tenantName, rather than tenantId, for NOVA_PROJECT_ID.  If you are using the
devstack sample data, you now need to set NOVA_PROJECT_ID to either 'admin'
or 'demo' (Before it expected '1' or '2').


 2. For now , a keystone server is running . And it seems only support OSAPI
 ...am I right ?  I dig many docs only talk about adding NOVA OSAPI enpoint
 templates , but no one talk about EC2 API(but EC2 features in source code).


I know that there has been work put into ec2 + keystone, but I have not
worked with it personally just yet.  Perhaps someone else has an update?

3. We can using cloud with Dashbord smoothly for basic usage. So does
 nova-client . I found that nova-client CLI tool could not
 add-key-pair/show-keypair ...I think it's fine , just add it direct from API
 endpoint .  But the problem is , nova boot can not assign key-pair while
 fire up an instance.


For server.create there is actually support in the underlying python library
for a key_name parameter (
https://github.com/rackspace/python-novaclient/blob/master/novaclient/v1_1/servers.py#L327),
but this has not yet been exposed through the CLI.  There is still work that
need to be done to catch the CLI up to the capabilities of the underlying
python library (keypairs, floating ips, security groups, volumes?)


 4. The workflow between all services and keystone , plz correct me.
 novaclient  keystone - nova -- keystone -
 novaclient
 glance client - keystone -- glance --keystone --
 glance client


Jesse summarized the flow for dashboard here, which  is related:
https://lists.launchpad.net/openstack/tif0lO7tn98ty.tif
https://lists.launchpad.net/openstack/msg04211.html

The main difference with novaclient vs. dash is that with novaclient the
tenant is specified, so the part where you use an unscoped token to grab a
tenant list is not needed.

Hope that helps!

On Thu, Oct 6, 2011 at 4:49 AM, Kuo Hugo tonyt...@gmail.com wrote:

 Hi folks ,

 After several days work on keystone / python-novaclient / glance

 There's some more questions want to discuss with everyone...

 1. What's the difference of python-novaclient between 
 devstackhttps://github.com/cloudbuilders/python-novaclient
  and rackspace https://github.com/rackspace/python-novaclient , as I
 know devstack's version forked from rackspace.. but while I install each of
 them... only devstack's python-novaclient worked fine with 
 Keystonehttps://github.com/cloudbuilders/keystone .
 Within rackspace version , always got Invalid OpenStack Nova Credentials
 how come ??

 2. For now , a keystone server is running . And it seems only support OSAPI
 ...am I right ?  I dig many docs only talk about adding NOVA OSAPI enpoint
 templates , but no one talk about EC2 API(but EC2 features in source code).

 3. We can using cloud with Dashbord smoothly for basic usage. So does
 nova-client . I found that nova-client CLI tool could not
 add-key-pair/show-keypair ...I think it's fine , just add it direct from API
 endpoint .  But the problem is , nova boot can not assign key-pair while
 fire up an instance.

 4. The workflow between all services and keystone , plz correct me.
 novaclient  keystone - nova -- keystone -
 novaclient
 glance client - keystone -- glance --keystone --
 glance client


 Cheers
 Hugo Kuo




 --
 +Hugo Kuo+
 tonyt...@gmail.com
 hugo@cloudena.com
 +886-935-004-793

 www.cloudena.com

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


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


Re: [Openstack] RBAC handled by keystone or each services ?

2011-10-06 Thread Joe Savak
Hi Kuo,
   RBAC is a hot topic at Essex right now with a few sessions to explicitly 
discuss them:

http://essexdesignsummit.sched.org/event/2610368e1c5bd0e52982777f75baafb5
http://essexdesignsummit.sched.org/event/2d4b84fe8559d6a144897a1d53adbb9e
http://essexdesignsummit.sched.org/event/6648ad6a353fd56d39d45193a69f6908

I'm sure notes will be shared about the Essex design summit soon.

In the meantime, Keystone tag 2011.03 provides the following functionality for 
roles:

1.   Core calls as defined in 
https://github.com/openstack/keystone/blob/master/keystone/content/admin/identityadminguide.pdf
 (should be fully  developed)

a.   GET /users/{user_id}/roles - returns global roles for a specific user 
(excludes tenant roles)

b.  GET /tenants/{tenantId}/users/{user_id}/roles - returns roles for a 
specific user on a specific tenant (excludes global roles)

2.   Extension calls as defined in 
https://github.com/openstack/keystone/blob/master/keystone/content/admin/OS-KSADM-admin-devguide.pdf
 (contract complete but not code complete)

a.   GET /OS-KSADM/roles - list roles

b.  POST /OS-KSADM/roles - add role

c.   GET /OS-KSADM/roles/{roleId} - get a role

d.  DELETE /OS-KSADM/roles/{roleId} - delete a role

Since the extension isn't complete yet,  you can use keystone-manage to add 
users, roles, etc for testing.

Thanks,
Joe

From: openstack-bounces+joe.savak=rackspace@lists.launchpad.net 
[mailto:openstack-bounces+joe.savak=rackspace@lists.launchpad.net] On 
Behalf Of Kuo Hugo
Sent: Wednesday, October 05, 2011 6:39 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] RBAC handled by keystone or each services ?

Hello folks ,

While playing with Keystone , there's four roles named 
[Admin,Member,KeystoneAdmin,KeystoneServiceAdmin].
I'm confusing about that who handles these roles's permission / privileges  
I mean RBAC include  admin, itsec, projectmanager, netadmin, developer roles in 
NOVA but not Admin/Member .
is that handled by keystone or service itself ???

Is there any API to add Roles(also set permission / privileges)?

In my guess , the RBAC still on each service(nova / swift ) , but how NOVA 
knows the permission of Role Admin ?


--
+Hugo Kuo+
tonyt...@gmail.commailto:tonyt...@gmail.com
hugo@cloudena.commailto:hugo@cloudena.com
+886-935-004-793

www.cloudena.comhttp://www.cloudena.com
This email may include confidential information. If you received it in error, 
please delete it.
___
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

2011-10-06 Thread Joseph Heck
That code update has already landed - its actually in the Diablo release, just 
not the default mechanism as yet. Carrot should be fully deprecated by the 
Essex release in favor of the Kombu AMQP library

-joe

On Oct 6, 2011, at 4:18 AM, Armaan wrote:
 i am asking this question out curiosity, Nova uses Carrot to connect with 
 RabbitMQ environment.
 But Carrot has already been discontinued in favor of Kombu framework.
 So in near future, is there any possibility that nova will use Kombu instead 
 of carrot.
 
 
 Regards
 Syed Armani
 ___
 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] Live Migration and Xen + Libvirt

2011-10-06 Thread masumotok
live migration + Xen is not tested in current version .
if you are in boston now and have xen environment, I may be able to help you.

Kei


差出人: openstack-bounces+masumotok=nttdata.co...@lists.launchpad.net 
[openstack-bounces+masumotok=nttdata.co...@lists.launchpad.net] は Rogério 
Vinhal Nunes [roge...@dcc.ufmg.br] の代理
送信日�r: 2011年10月7日 2:42
宛先: openstack
件名: [Openstack] Live Migration and Xen + Libvirt

I'm trying to make live migration work in an environment with Xen and Libvirt, 
but I found some issues.

The first one I managed to correct, but it really looks like a bug. The live 
migration command will fail and the logs will indicate InstanceNotRunning. 
That's because when a xen virtual machine is not using the processor, its 
status is blocked. I corrected it by sending the instance in an infinite 
CPU loop and waiting for nova-compute to update the DB with the status 
running. I don't know how these status are handled by KVM, but at least the 
migration check should take that in consideration if it plans to work with xen.

The second one is a little more complicated and I haven't found a solution yet, 
so you may help me with it. After making the vm running the live migration 
just fails and the logs rise an error Cannot find 'model'. Is there any 
configuration that is related to this?

trace from nova-manage.log:

(nova): TRACE: Traceback (most recent call last):
(nova): TRACE:   File /usr/bin/nova-manage, line 2141, in module
(nova): TRACE: main()
(nova): TRACE:   File /usr/bin/nova-manage, line 2129, in main
(nova): TRACE: fn(*fn_args, **fn_kwargs)
(nova): TRACE:   File /usr/bin/nova-manage, line 987, in live_migration
(nova): TRACE: self._migration(ec2_id, dest)
(nova): TRACE:   File /usr/bin/nova-manage, line 976, in _migration
(nova): TRACE: block_migration: block_migration}})
(nova): TRACE:   File /usr/lib/pymodules/python2.6/nova/rpc/__init__.py, line 
45, in call
(nova): TRACE: return get_impl().call(context, topic, msg)
(nova): TRACE:   File /usr/lib/pymodules/python2.6/nova/rpc/impl_kombu.py, 
line 739, in call
(nova): TRACE: rv = list(rv)
(nova): TRACE:   File /usr/lib/pymodules/python2.6/nova/rpc/impl_kombu.py, 
line 703, in __iter__
(nova): TRACE: raise result
(nova): TRACE: RemoteError: RemoteError Error cannot find 'model'
___
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] Introducing the CDN As a Service project

2011-10-06 Thread Balle, Susanne
Stakers,

It's been brought to my attention that the announcement of the CDN as a Service 
project may have implied that the project is an incubated or official OpenStack 
project. To be clear, it is not, and I was merely attempting to introduce the 
concept and encourage feedback.

Susanne


From: openstack-bounces+susanne.balle=hp@lists.launchpad.net 
[mailto:openstack-bounces+susanne.balle=hp@lists.launchpad.net] On Behalf 
Of Balle, Susanne
Sent: Thursday, October 06, 2011 7:36 AM
To: openstack@lists.launchpad.net; Bob Melander; ajeet.ba...@vce.com; Hareesh 
Puthalath
Subject: [Openstack] Introducing the OpenStack CDN As a Service project

Hello Stackers!

Based on the great feedback from our Monday session here at the Openstack 
summit we have created an Openstack CDN As A Service project on launchpad.

The CDN Service is a framework to enable OpenStack services (storage and 
compute) to interact with a variety of CDN providers. It consists of a Service 
Layer APIs, a control fabric, and an extension mechanism to allow open or 
proprietary vendors of CDN services to plug in. Other use-cases such as Live 
streaming will also be considered.

https://launchpad.net/cndaas

The group will work towards the following goals:

1. Define a Service layer APIs
2. Understand how do we best integrate with the CDN providers
3. Define the origin server/end-point in a consistent way across all form of 
storages, compute, etc..
4. Define CDN public URI
5. Create an implementation of the Service.

We have a lot of work in front of us so if you are interested in contributing 
to this great project please join the CDN as a Service team:

https://launchpad.net/~cdnaas-core

Looking forward to hearing from you

Susanne Balle
___
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] Does diablo support lvm block devices instead files for VMs?

2011-10-06 Thread Roman Sokolkov
Hi! For my research I think Diablo doesn't support LVM block devices for
VMs, does it?

In /usr/share/nova/libvirt.xml.template only file supports for main disk
device. I am right?

#if $getVar('rescue', False)
disk type='file'
driver type='${driver_type}'/
source file='${basepath}/disk.rescue'/
target dev='${disk_prefix}a' bus='${disk_bus}'/
/disk
disk type='file'
driver type='${driver_type}'/
source file='${basepath}/disk'/
target dev='${disk_prefix}b' bus='${disk_bus}'/
/disk
#else
#if not ($getVar('ebs_root', False))
disk type='file'
driver type='${driver_type}'/
source file='${basepath}/disk'/
target dev='${root_device}' bus='${disk_bus}'/
/disk
#end if

Thanks
___
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] Live Migration and Xen + Libvirt

2011-10-06 Thread Rogério Vinhal Nunes
Yes, I know it hasn't been tested, but as libvirt's interface is quite
similar, I was hoping to make it work with xen. This would also be nice for
openstack to broad its officially tested support.

I'm afraid I'm not even close to Boston, I'm frequently working in this
environment, so any clues and suggestions could help.

2011/10/6 masumo...@nttdata.co.jp

 live migration + Xen is not tested in current version .
 if you are in boston now and have xen environment, I may be able to help
 you.

 Kei

 
 差出人: 
 openstack-bounces+masumotok=nttdata.co...@lists.launchpad.net[openstack-bounces+masumotok=
 nttdata.co...@lists.launchpad.net] は Rogério Vinhal Nunes [
 roge...@dcc.ufmg.br] の代理
 送信日�r: 2011年10月7日 2:42
 宛先: openstack
 件名: [Openstack] Live Migration and Xen + Libvirt

 I'm trying to make live migration work in an environment with Xen and
 Libvirt, but I found some issues.

 The first one I managed to correct, but it really looks like a bug. The
 live migration command will fail and the logs will indicate
 InstanceNotRunning. That's because when a xen virtual machine is not using
 the processor, its status is blocked. I corrected it by sending the
 instance in an infinite CPU loop and waiting for nova-compute to update the
 DB with the status running. I don't know how these status are handled by
 KVM, but at least the migration check should take that in consideration if
 it plans to work with xen.

 The second one is a little more complicated and I haven't found a solution
 yet, so you may help me with it. After making the vm running the live
 migration just fails and the logs rise an error Cannot find 'model'. Is
 there any configuration that is related to this?

 trace from nova-manage.log:

 (nova): TRACE: Traceback (most recent call last):
 (nova): TRACE:   File /usr/bin/nova-manage, line 2141, in module
 (nova): TRACE: main()
 (nova): TRACE:   File /usr/bin/nova-manage, line 2129, in main
 (nova): TRACE: fn(*fn_args, **fn_kwargs)
 (nova): TRACE:   File /usr/bin/nova-manage, line 987, in live_migration
 (nova): TRACE: self._migration(ec2_id, dest)
 (nova): TRACE:   File /usr/bin/nova-manage, line 976, in _migration
 (nova): TRACE: block_migration: block_migration}})
 (nova): TRACE:   File /usr/lib/pymodules/python2.6/nova/rpc/__init__.py,
 line 45, in call
 (nova): TRACE: return get_impl().call(context, topic, msg)
 (nova): TRACE:   File
 /usr/lib/pymodules/python2.6/nova/rpc/impl_kombu.py, line 739, in call
 (nova): TRACE: rv = list(rv)
 (nova): TRACE:   File
 /usr/lib/pymodules/python2.6/nova/rpc/impl_kombu.py, line 703, in __iter__
 (nova): TRACE: raise result
 (nova): TRACE: RemoteError: RemoteError Error cannot find 'model'

___
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] Creating openstack-dev mailing list

2011-10-06 Thread Leandro Reox
Stefano,

How is the rest of the community going to participate or leave their opinion
on why some design path is going to be taken, or maybe leave their feedback
of why an arquitecture change is going to be made. Will be an open list ? or
just for few ?
Will be launchapd the only way to interact with the developers ? . The
openstack-operators lists, that i thinks is for usage and implementation
already exist and its pretty abandoned.
For us, with a pretty big openstack schema running in production,
participating on this mailing list, is critical for future architecture
designs decisions ( multi cluster zoning, ram based scheduling, nova-volumes
farm ) . And i believe that splitting the list will be end up o
non-attention at all.
We enjoy a lot moderating and helping out on the forums, but when we hit a
desing flaw or a major doubt, probable hitting some strange issue,  here is
were we get quickiest te best and right answer (launchpad questions could
take a whle, and not everyone is checking registered issues everyday,
and an email is simpler)
Dont wanna sound like a change-ressitance guy buy this are just my concerns

Best Regard !
LeanReox

On Thu, Oct 6, 2011 at 8:46 PM, Jay Pipes jaypi...@gmail.com wrote:

 I would not be opposed to this. I think we may have reached that
 critical mass where a split makes sense now.

 -jay

 On Thu, Oct 6, 2011 at 1:35 PM, Stefano Maffulli stef...@openstack.org
 wrote:
  Jesse Andrews (anotherjesse)(Rackspace)
  Jonathan Bryce (jbryce)(Rackspace)
  Devin Carlen (devcamcar)(Nebula)
  Thierry Carrez (ttx)(Rackspace)
  John Dickinson (notmyname)(Rackspace))
  Vish Ishaya (vishy)(Rackspace)
  Josh Kearney (jk0)(Rackspace)
  Joshua McKenty (jmckenty)(Piston)
  Ewan Mellor (ewanmellor)(Citrix)
  Jay Pipes (jaypipes)(Rackspace)
  John Purrier (johnpur)(HP)
  Monty Taylor (mordred)(Rackspace)
  Paul Voccio (pvo)(Rackspace)
  Ziad Sawalha (zns)(Rackspace)
 
  Hello folks,
 
  I've been talking to quite a few developers participating to the Design
  Summit and a recurring request I got is to create a new mailing list for
  the OpenStack developers to meet and discuss.
 
  There is also a concern that putting developers in another list will
  decrease their attention to the bigger part of the community. I believe
  this is a serious concern and that it's going to be our role as leaders
  of this community to prevent this from happening.
 
  I'd suggest to dedicate the existing mailing list for discussions about
  usage of OpenStack (deployment and development of applications on top of
  OpenStack API) and create a new one only for developers of OpenStack.
  Developers in this context should be developers of openstack projects
  (nova, swift, quantum, etc).
 
  If there is no opposition to this proposal in the next days, I'll
  proceed and create openstack-dev and invite developers to subscribe to
  it.
 
  cheers,
  stef
 
 
  ___
  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] Creating openstack-dev mailing list

2011-10-06 Thread John Purrier
My 2 cents...

The traffic on the list is less than 100 messages per day, of that about 35%
is bug notifications. I wonder if we redirect the developer oriented email
on the list whether we will have 10 messages a day on the original openstack
mailing list.

Stefano, can you elaborate on why the developers feel a split is necessary
at this point? Most (if not all) of the traffic is developer oriented, what
is the problem we want to solve?

Thanks,

John 

-Original Message-
From: openstack-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
Of Stefano Maffulli
Sent: Thursday, October 06, 2011 1:35 PM
To: openstack
Subject: [Openstack] Creating openstack-dev mailing list

Jesse Andrews (anotherjesse)(Rackspace)
Jonathan Bryce (jbryce)(Rackspace)
Devin Carlen (devcamcar)(Nebula)
Thierry Carrez (ttx)(Rackspace)
John Dickinson (notmyname)(Rackspace))
Vish Ishaya (vishy)(Rackspace)
Josh Kearney (jk0)(Rackspace)
Joshua McKenty (jmckenty)(Piston)
Ewan Mellor (ewanmellor)(Citrix)
Jay Pipes (jaypipes)(Rackspace)
John Purrier (johnpur)(HP)
Monty Taylor (mordred)(Rackspace)
Paul Voccio (pvo)(Rackspace)
Ziad Sawalha (zns)(Rackspace)

Hello folks,

I've been talking to quite a few developers participating to the Design
Summit and a recurring request I got is to create a new mailing list for
the OpenStack developers to meet and discuss.  

There is also a concern that putting developers in another list will
decrease their attention to the bigger part of the community. I believe
this is a serious concern and that it's going to be our role as leaders
of this community to prevent this from happening.

I'd suggest to dedicate the existing mailing list for discussions about
usage of OpenStack (deployment and development of applications on top of
OpenStack API) and create a new one only for developers of OpenStack.
Developers in this context should be developers of openstack projects
(nova, swift, quantum, etc).

If there is no opposition to this proposal in the next days, I'll
proceed and create openstack-dev and invite developers to subscribe to
it.

cheers,
stef


___
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