[Openstack] About volume recover after reboot a compute node.

[Sam Su]

Hi,

I have a mini Openstack cloud based on Essex, there are one compute
node with nova-volumes and one control node in this environment. In the
compute node, there is an instance attached it's volume. After reboot the
compute node, the instance lost it's volume, but the instance is still
attached the volume in the database.
I am wondering how to recover volume to attach it's instance after the host
compute node is rebooted?

It's much appreciated if someone can give me some tips.

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

[Openstack] unsubscribe

[Alexey Eromenko]

-- 
-Alexey Eromenko "Technologov"

___
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] [Devstack]Keystone authentication problem when installing

[Vaze, Mandar]

May be related to https://bugs.launchpad.net/keystone/+bug/995976
Check last comment at https://bugs.launchpad.net/keystone/+bug/995811

-Mandar

From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net 
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On 
Behalf Of Ke Wu
Sent: Thursday, June 28, 2012 7:01 AM
To: openstack mail list
Subject: [Openstack] [Devstack]Keystone authentication problem when installing

Hi,

I can't find a mailing list of devstack so I choose to ask here, hope this 
doesn't spam you guys.

I was trying to build Devstack on my VM (Ubuntu 12.04 server) to start a new 
environment for Horizon development.

Everything went well until it hit the point to start Keystone service, the 
error msg was:

Expecting authentication method via
  either a service token, --token or env[SERVICE_TOKEN],
  or credentials, --os_username or env[OS_USERNAME].
+ NOVA_USER_ID=
++ get_field 1
++ read data
++ grep ' service '
++ keystone tenant-list
Expecting authentication method via
  either a service token, --token or env[SERVICE_TOKEN],
  or credentials, --os_username or env[OS_USERNAME].
+ NOVA_TENANT_ID=
++ keystone ec2-credentials-create --user --tenant_id
usage: keystone ec2-credentials-create [--user_id ]
   [--tenant_id ]
keystone ec2-credentials-create: error: argument --user_id: expected one 
argument
+ CREDS=
++ failed
++ local r=2
++ set +o xtrace

Anybody has an idea why this happened?

Thanks!

-Ke Wu

__
Disclaimer:This email and any attachments are sent in strictest confidence for 
the sole use of the addressee and may contain legally privileged, confidential, 
and proprietary data.  If you are not the intended recipient, please advise the 
sender by replying promptly to this email and then delete and destroy this 
email and any attachments without any further use, copying or forwarding___
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] [devstack] Recent updates

[Dean Troyer]

A quick summary of recent significant DevStack changes:

* Keystone Service Catalog SQL back-end
Add "KEYSTONE_CATALOG_BACKEND=sql" to localrc to tell Keystone to use
the SQL backend for the service catalog.  This enables the keystone
service-* and endpoint-* commands to manage the service catalog. See
files/keystone_data.sh for the default commands used by DevStack.
DevStack continues to use the templated service catalog by default.


* Remove default services from ENABLED_SERVICES
This change allows easy the removal of services that are in
ENABLED_SERVICES by default (see the list in stackrc) by appending the
service name prefixed with a '-' to ENABLED_SERVICES.  For example, to
switch from Nova Volumes to Cinder, you would add this to localrc:

ENABLED_SERVICES+=,-n-vol,c-api,c-sch,c-vol

(Note the leading comma following the equals sign)


* Cinder Support
Speaking of Cinder, basic support was merged last week.  Since it is
still a bit of a moving target additional updates may still be
required.  Enable Cinder as shown in the ENABLED_SERVICES section
above.  Nova Volume will remain DevStack's default until some time
after Cinder becomes the default in Nova.
  * The default volume group name has changed to stack-volumes to
remove the nova project name (it was formerly nova-volumes).  Set it
in localrc with VOLUME_GROUP.
  * The default backing file is now
/opt/stack/data/stack-volumes-backing-file (it was formerly
/opt/stack/nova-volumes-backing-file).  Set it in localrc with
VOLUME_NAME_PREFIX.


* Colored logs
Vish added color to Nova's logs a couple of weeks ago to greatly help
visually scanning the log files.  Set "LOG_COLOR=False" in localrc to
disable the color as it is enabled by default.  Also note that if
SYSLOG=true the log coloring is also disabled.


dt

-- 

Dean Troyer
dtro...@gmail.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

Re: [Openstack] [Devstack]Keystone authentication problem when installing

[Ke Wu]

Here is my localrc:

ENABLED_SERVICES="$ENABLED_SERVICES,swift"
MYSQL_PASSWORD=password
ADMIN_PASSWORD= password 
RABBIT_PASSWORD= password
SERVICE_TOKEN= password
SWIFT_HASH= password
HOST_IP=10.0.0.0
RECLONE=yes
SERVICE_PASSWORD= password

By what distribution you mean? I clone the devstack code project from github.

Thanks,

-K

On Jun 27, 2012, at 6:44 PM, Adam Young wrote:

> Can you post your localrc file?  YOu can blank out the passwords.
> 
> Also,  what distribution?
> 
> 
> On 06/27/2012 09:30 PM, Ke Wu wrote:
>> Hi,
>> 
>> I can't find a mailing list of devstack so I choose to ask here, hope this 
>> doesn't spam you guys.
>> 
>> I was trying to build Devstack on my VM (Ubuntu 12.04 server) to start a new 
>> environment for Horizon development. 
>> 
>> Everything went well until it hit the point to start Keystone service, the 
>> error msg was:
>> 
>> Expecting authentication method via 
>>   either a service token, --token or env[SERVICE_TOKEN], 
>>   or credentials, --os_username or env[OS_USERNAME].
>> + NOVA_USER_ID=
>> ++ get_field 1
>> ++ read data
>> ++ grep ' service '
>> ++ keystone tenant-list
>> Expecting authentication method via 
>>   either a service token, --token or env[SERVICE_TOKEN], 
>>   or credentials, --os_username or env[OS_USERNAME].
>> + NOVA_TENANT_ID=
>> ++ keystone ec2-credentials-create --user --tenant_id
>> usage: keystone ec2-credentials-create [--user_id ]
>>[--tenant_id ]
>> keystone ec2-credentials-create: error: argument --user_id: expected one 
>> argument
>> + CREDS=
>> ++ failed
>> ++ local r=2
>> ++ set +o xtrace
>> 
>> Anybody has an idea why this happened?
>> 
>> Thanks!
>> 
>> -Ke Wu
>> 
>> 
>> ___
>> 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

[Openstack] Where can I get the nova-volumes info?

[Sam Su]

Hi,

 I have a formatted nova-volume disk, if cannot associate the volume disk
to a VM, does anyone knows where can I find out the volume disk format
(such as ext3 or ext4)?

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

Re: [Openstack] [Devstack]Keystone authentication problem when installing

[Adam Young]

Can you post your localrc file?  YOu can blank out the passwords.

Also,  what distribution?


On 06/27/2012 09:30 PM, Ke Wu wrote:

Hi,

I can't find a mailing list of devstack so I choose to ask here, hope 
this doesn't spam you guys.


I was trying to build Devstack on my VM (Ubuntu 12.04 server) to start 
a new environment for Horizon development.


Everything went well until it hit the point to start Keystone service, 
the error msg was:


Expecting authentication method via
either a service token, --token or env[SERVICE_TOKEN],
  or credentials, --os_username or env[OS_USERNAME].
+ NOVA_USER_ID=
++ get_field 1
++ read data
++ grep ' service '
++ keystone tenant-list
Expecting authentication method via
either a service token, --token or env[SERVICE_TOKEN],
  or credentials, --os_username or env[OS_USERNAME].
+ NOVA_TENANT_ID=
++ keystone ec2-credentials-create --user --tenant_id
usage: keystone ec2-credentials-create [--user_id ]
   [--tenant_id ]
keystone ec2-credentials-create: error: argument --user_id: expected 
one argument

+ CREDS=
++ failed
++ local r=2
++ set +o xtrace

Anybody has an idea why this happened?

Thanks!

-Ke Wu


___
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] [Devstack]Keystone authentication problem when installing

[Ke Wu]

Hi,

I can't find a mailing list of devstack so I choose to ask here, hope this 
doesn't spam you guys.

I was trying to build Devstack on my VM (Ubuntu 12.04 server) to start a new 
environment for Horizon development. 

Everything went well until it hit the point to start Keystone service, the 
error msg was:

Expecting authentication method via 
  either a service token, --token or env[SERVICE_TOKEN], 
  or credentials, --os_username or env[OS_USERNAME].
+ NOVA_USER_ID=
++ get_field 1
++ read data
++ grep ' service '
++ keystone tenant-list
Expecting authentication method via 
  either a service token, --token or env[SERVICE_TOKEN], 
  or credentials, --os_username or env[OS_USERNAME].
+ NOVA_TENANT_ID=
++ keystone ec2-credentials-create --user --tenant_id
usage: keystone ec2-credentials-create [--user_id ]
   [--tenant_id ]
keystone ec2-credentials-create: error: argument --user_id: expected one 
argument
+ CREDS=
++ failed
++ local r=2
++ set +o xtrace

Anybody has an idea why this happened?

Thanks!

-Ke Wu___
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] storage backend for nova

[udit agarwal]

Hi,
 I have set up Openstack in my lab with everything except storage nodes on
one system and two other systems with each of them acting themselves as a
storage node. I have used swift as the backend for glance so all the
uploaded images are stored on these storage nodes. But when I run a virtual
machine using nova, it reads the image from the storage nodes and it seems
to me that it uses the local filesystem for storing instances and after I
shutoff my virtual machine, it writes back to the storage nodes. But the
thing that I want to implement is that if I copy some file from my local
system to that virtual machine, it should automatically get stored on my
storage nodes rather than occupying space on my local filesystem.

 Can anybody help me with this??
 Thanks in advance.

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

Re: [Openstack] Nova and asynchronous instance launching

[Doug Davis]

Consider the creation of a "Job" type of entity that will be returned from 
the original call - probably a 202.  Then the client can check the Job to 
see how things are going.
BTW - this pattern can be used for any async op, not just the launching of 
multiple instances since technically any op might be long-running (or 
queued) based on the current state of the system. 

thanks
-Doug
__
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  d...@us.ibm.com
The more I'm around some people, the more I like my dog.



Devin Carlen  
Sent by: openstack-bounces+dug=us.ibm@lists.launchpad.net
06/27/2012 03:53 PM

To
"openstack@lists.launchpad.net (openstack@lists.launchpad.net)" 

cc

Subject
[Openstack] Nova and asynchronous instance launching






We filed a blueprint for this yesterday:

https://blueprints.launchpad.net/nova/+spec/launch-instances-async

"Currently if a user attempts to create a lot of instances with a single 
API call (using min_count) the request will hang for a long time while all 
RPC calls are completed. For a large number of instances this can take a 
very long time. The API should return immediately and asynchronously make 
RPC calls."

We are looking for creative ways to work around this problem, but in the 
meantime I'd like to hear from folks on what they think the preferred 
solution would be.


Devin___
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] running HA cluster of guests within openstack

[Pádraig Brady]

On 04/13/2012 12:53 PM, Pádraig Brady wrote:
> On 04/13/2012 10:31 AM, ikke wrote:
>> I likely am not the first one to ask this, but since I didn't find a
>> thread about it I start one.
>>
>> Is there any shared experience available what are the capabilities of
>> OpenStack to run cluster of guests in the cloud? Do you have
>> experience of the following questions, or links to more info? The
>> questions relate to running a legacy HA cluster in virtual env, and
>> moving it into cloud...
> 
> I'll just point out two early stage projects
> that used in combination can provide a HA solution.
> 
> http://wiki.openstack.org/Heat
> http://wiki.openstack.org/ResourceMonitorAlertsandNotifications
> 
> These are similar to AWS CloudFormations and CloudWatch respectively.

I notice Heat V4 has just been released.

Here is some additional info on High Availability:
https://github.com/heat-api/heat/wiki/Roadmap-Feature:-High-Availability

and some notes on using it in its current form:
https://github.com/heat-api/heat/wiki/Using-HA

cheers,
Pádraig.

___
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] integrating Quantum and Ceilometer

[Doug Hellmann]

On Wed, Jun 27, 2012 at 5:48 PM, Dan Wendlandt  wrote:

> Hi Doug,
>
> Thanks for sending this out.  Pinging the ceilometer team about Quantum
> support has been on my todo list for a while now.
>
> Troy (CC'd) did some thinking about notifications for quantum, but we
> haven't implemented this yet.  Here's the existing blueprint:
> https://blueprints.launchpad.net/quantum/+spec/quantum-notifications .
>  My assumption is that we would model what Nova is doing for notifications,
> but to be honest, I'm not really familiar with that code.  Anyone
> interested in taking this blueprint on?
>

Using the nova-based notifications library would make it very easy to tie
in with the work we have already done to catch compute notifications. The
libraries for notifications were just moved into openstack.common, which
will make them easy for you to pick up and reuse.


> We do have an extension to support port-statistics to indicate the amount
> of traffic sent to/from a VM that could be used by ceilometer, though that
> would likely be more of a poll model, at least with the current
> implementation.
>

That makes sense, and is similar to what we're doing for things like CPU
and disk I/O by polling libvirt.

One thing that comes up frequently is the desire to only charge for traffic
"outside" of a cloud. Do the ports know how to tell the difference between
internal and external traffic?


>
> Dan
>
> On Wed, Jun 27, 2012 at 3:16 PM, Doug Hellmann <
> doug.hellm...@dreamhost.com> wrote:
>
>> Hello,
>>
>> As part of the ceilometer project¹, we're working on retrieving usage
>> data from various OpenStack components. We would like to integrate
>> with Quantum for information about network resource utilization that a
>> deployer might want to bill their tenants for.
>>
>> Ceilometer has a plugin-based architecture, which makes it easy to add
>> new measurement types and data collectors. Our approach with other
>> measurements is to collect everything and let the ceilometer user decide
>> what to bill for and what to ignore (they can turn off measurements for
>> things they do not care about).
>>
>> Depending on the project and the type of data, we can either
>> use the notification events generated by allocating/deallocating
>> a resource, or we can poll for metrics being collected elsewhere.
>> We will probably want to use both approaches for integrating
>> with Quantum (e.g., use events for things like IP allocation and
>> polling for I/O).
>>
>> Do you have any advice on how to integrate Ceilometer and Quantum?
>> For example, does Quantum emit notifications and does it collect
>> (or provide an API to query) I/O statistics?
>>
>> Thanks,
>> Doug
>>
>>
>> ¹  http://launchpad.net/ceilometer
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> ~~~
> 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] [metering] integrating Quantum and Ceilometer

[Dan Wendlandt]

Hi Doug,

Thanks for sending this out.  Pinging the ceilometer team about Quantum
support has been on my todo list for a while now.

Troy (CC'd) did some thinking about notifications for quantum, but we
haven't implemented this yet.  Here's the existing blueprint:
https://blueprints.launchpad.net/quantum/+spec/quantum-notifications .  My
assumption is that we would model what Nova is doing for notifications, but
to be honest, I'm not really familiar with that code.  Anyone interested in
taking this blueprint on?

We do have an extension to support port-statistics to indicate the amount
of traffic sent to/from a VM that could be used by ceilometer, though that
would likely be more of a poll model, at least with the current
implementation.

Dan

On Wed, Jun 27, 2012 at 3:16 PM, Doug Hellmann
wrote:

> Hello,
>
> As part of the ceilometer project¹, we're working on retrieving usage
> data from various OpenStack components. We would like to integrate
> with Quantum for information about network resource utilization that a
> deployer might want to bill their tenants for.
>
> Ceilometer has a plugin-based architecture, which makes it easy to add
> new measurement types and data collectors. Our approach with other
> measurements is to collect everything and let the ceilometer user decide
> what to bill for and what to ignore (they can turn off measurements for
> things they do not care about).
>
> Depending on the project and the type of data, we can either
> use the notification events generated by allocating/deallocating
> a resource, or we can poll for metrics being collected elsewhere.
> We will probably want to use both approaches for integrating
> with Quantum (e.g., use events for things like IP allocation and
> polling for I/O).
>
> Do you have any advice on how to integrate Ceilometer and Quantum?
> For example, does Quantum emit notifications and does it collect
> (or provide an API to query) I/O statistics?
>
> Thanks,
> Doug
>
>
> ¹  http://launchpad.net/ceilometer
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


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

[Openstack] Call for proposals for linux.conf.au 2013

[Anne Gentle]

Hi all -

July 6th is the deadline for proposals related to open source for
linux.conf.au 2013. See http://linux.conf.au/cfp for more info. There
are three ways to present:

Presentations
Presentations are 40 minute slots that are generally presented in
lecture format. These form the bulk of the available conference slots.
Tutorials
Tutorials are 90 minutes that are generally presented in a
classroom format. They should be interactive or hands-on in nature.
Tutorials are expected to have a specific learning outcome for
attendees.
Miniconferences
Miniconfs are day-long sessions on a specific topic.

Happy info sharing!
Anne

___
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] HVM + Xen Hypervisor via libvirt possible?

[Jim Fehlig]

Daniel P. Berrange wrote:
> On Fri, Jun 22, 2012 at 12:17:11AM +0800, Huang Zhiteng wrote:
>   
>> Of course it is possible.  What kind of issue did you run into?
>>
>> On Thu, Jun 21, 2012 at 5:52 PM, Wang Li  wrote:
>> 
>>> hi,all
>>>
>>> I need to run virtual machines on Xen Hypervisor in HVM mode,
>>> is it possible when using libvirt?
>>>   
>
> Actually, this is not currently possible. For reasons I don't
> know, the libvirt driver currently hardcodes use of paravirtualized
> guests when connected to Xen hosts. It does not allow use of HVM
> guests.  There's no particularly good technical reason why it can't
> be made to work.

Right.  I've been working on this in my few spare cycles and hope to
post some patches soon.

>  There'd need to be a way to tag instance types
> with HVM vs paravirt, in addition to their architecture.

I was hoping to just use the vm_mode image property that the XenServer
folks use.  See option 2 in this mail

https://lists.launchpad.net/openstack/msg11507.html

>  The
> libvirt driver would have to expose whether each host supports
> paravirt or HVM or both. The schedular would then have to take
> this into account when placing guests.
>   

I posted an RFC patch here that filters hosts based on the vm_mode image
property and the additional_compute_capabilities flag.  I haven't
received any comments, so should probably just push this to gerrit.

Regards,
Jim


___
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] (no subject)

[Vishvananda Ishaya]

This looks like virus initiated spam to me. I recommend not clicking this link

Vish

On Jun 27, 2012, at 1:15 PM, Jayashree(Jay) Beltur wrote:

> http://katierefling.com/blog/wp-content/themes/pyrmont-v2/ybkrz.html
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

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

[Openstack] (no subject)

[Jayashree(Jay) Beltur]

http://katierefling.com/blog/wp-content/themes/pyrmont-v2/ybkrz.html___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [keystone] proposing adding Adam Young (ayoung) to keystone-core

[Chmouel Boudjnah]

+1!

On Wed, Jun 27, 2012 at 9:47 PM, Devin Carlen  wrote:
> +1!
>
> On Jun 27, 2012, at 12:44 AM, Syed Armani wrote:
>
>
> Adam is a great guy, He is always there if you need any help or guidance.
> His work is incredible.
>
> Best!
> Syed
>
> On Wed, Jun 27, 2012 at 12:57 PM, Razique Mahroua
>  wrote:
>>
>> Not part of that group, but Adam's work is indeed fantastic
>>
>> Nuage & Co - Razique Mahroua
>> razique.mahr...@gmail.com
>>
>> 
>>
>> Le 26 juin 2012 à 23:06, Joseph Heck a écrit :
>>
>> Given his work in Keystone since the redux, I would like propose Adam
>> Young (ayoung) be added to the group keystone-core.
>>
>> For a process in doing this, I thought we'd generally follow Nova's
>> core-promotion process = lazy consensus over a week, and assuming no -1's
>> and at least two +1's from current core members, it's good to go.
>>
>> -joe
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

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

[Openstack] Nova and asynchronous instance launching

[Devin Carlen]

We filed a blueprint for this yesterday:

https://blueprints.launchpad.net/nova/+spec/launch-instances-async

"Currently if a user attempts to create a lot of instances with a single API 
call (using min_count) the request will hang for a long time while all RPC 
calls are completed. For a large number of instances this can take a very long 
time. The API should return immediately and asynchronously make RPC calls."

We are looking for creative ways to work around this problem, but in the 
meantime I'd like to hear from folks on what they think the preferred solution 
would be.


Devin___
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] proposing adding Adam Young (ayoung) to keystone-core

[Devin Carlen]

+1!

On Jun 27, 2012, at 12:44 AM, Syed Armani wrote:

> 
> Adam is a great guy, He is always there if you need any help or guidance. His 
> work is incredible.
> 
> Best!
> Syed
> 
> On Wed, Jun 27, 2012 at 12:57 PM, Razique Mahroua  
> wrote:
> Not part of that group, but Adam's work is indeed fantastic
> 
> Nuage & Co - Razique Mahroua 
> razique.mahr...@gmail.com
> 
> 
> 
> Le 26 juin 2012 à 23:06, Joseph Heck a écrit :
> 
>> Given his work in Keystone since the redux, I would like propose Adam Young 
>> (ayoung) be added to the group keystone-core.
>> 
>> For a process in doing this, I thought we'd generally follow Nova's 
>> core-promotion process = lazy consensus over a week, and assuming no -1's 
>> and at least two +1's from current core members, it's good to go.
>> 
>> -joe
>> 
>> 
>> 
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Openstack] [Swift] Problem with merging

[Chmouel Boudjnah]

This has been fixed and merged now, thanks CI team for the great work.

Chmouel.

On Wed, Jun 27, 2012 at 7:10 PM, John Postlethwait
 wrote:
> Jenkins has been broken since yesterday. The infrastructure team is trying
> to address that now, it will merge when it is back up.
>

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

Re: [Openstack] glance access error from remote client

[Xin Zhao]

Hi Jay,

I thought about that, and changed the client environment variables to 
use the FQDN of the controller, I even restarted glance/swift services 
with the controller FQDN in the config files (127.0.0.1/localhost are
the original values). I compared the OS_XXX env between the controller 
node and remote client, they are the same.


What's interesting is that, even if I give a wrong hostname or port 
number in the command "glance index --host=XXX --port=XXX", it still 
works if run on the controller node.
And, strace shows, from the remote client node, that 127.0.0.1:9292 is 
connected instead of the hostname:9292 specified in the command line.


So how can I make sure the client does talk to THE hostname, instead of 
127.0.0.1 ?


Thanks,
Xin


On 6/27/2012 11:40 AM, Jay Pipes wrote:

On 06/27/2012 10:04 AM, Xin Zhao wrote:

Hello,

I have an Essex install of openstack on RHEL6. The controller node has
all openstack services running, and there
are several separate compute nodes.  Now I have a problem using glance.

If I issue "glance index --host=XXX --port=9292" on the controller node,
it works fine.

If I issue the same command from a remote client node, where I have all
the relevant openstack rpms installed, it
fails with the following error message:

Failed to show index. Got error:
There was an error connecting to a server
Details: [Errno 111] Connection refused


This usually because the glance CLI tool is trying to connect to the 
localhost (which obviously isn't running the Glance API server). Have 
you looked at the difference between your OS_XXX environment variables 
between the controller node and the remote client node? It may be that 
when you are doing a glance index --host=XXX --port=9292 on the 
controller node that the glance CLI tool is actually connecting to 
localhost/127.0.0.1, but I'm not completely sure..


Best,
-jay

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





smime.p7s
Description: S/MIME Cryptographic Signature
___
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] Jenkins

[John Postlethwait]

Yes, it is currently being worked on...

John Postlethwait
Nebula, Inc.


On Wednesday, June 27, 2012 at 10:04 AM, Gary Kotton wrote:

> Hi,
> Is anyone aware of a problem with Jenkins?
> Thanks
> Gary
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net (mailto: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] Jenkins

[Chris Behrens]

It had some problems… now it just seems backed up…  trying to catch up.


On Jun 27, 2012, at 12:04 PM, Gary Kotton wrote:

> Hi,
> Is anyone aware of a problem with Jenkins?
> Thanks
> Gary
> 
> ___
> 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] Heat Version 4 Released

[Ian Main]

The Heat developers are pleased to announce the release of the Heat API
version 4.  We have added many new features including Ubuntu Precise
host support.

Heat is a project designed to work with OpenStack that provides a
programmable interface to orchestrate multiple cloud applications
implementing CloudFormation.


To give it a spin on Fedora 17:

https://github.com/heat-api/heat/blob/master/docs/GettingStarted.rst#readme

Or on Ubuntu 12.04:

https://github.com/heat-api/heat/wiki/Getting-Started-with-Heat-using-Master-on-Ubuntu

Enhancements in version 4:

+ Cloud Watch high availability.
  Heat monitors services and VMs and can restart them or send alarms
  on failure.  Also supported is escalation of service failure which can
  result in an instance restart.  This is similar to the AWS CloudWatch
  functionality.
  https://github.com/heat-api/heat/wiki/Roadmap-Feature:-High-Availability

+ Authentication and identification.  
  Heat now performs proper authentication on all API calls, identifying
  individual users, and creating stacks on a per-user basis.  Heat now
  also supports AWS style keys as well as keystone username/password or
  token authentication.
  
https://github.com/heat-api/heat/wiki/Roadmap-Feature:-Associate-users-with-templates-using-keystone

+ Nested stack support.
  Heat templates can now reference other templates enabling you to use
  them as building blocks to create larger deployments.
  https://github.com/heat-api/heat/wiki/Roadmap-Feature:-Nested-stacks

+ IAM::User support.
  
https://github.com/heat-api/heat/wiki/Roadmap-Feature:-AWS-template-support-parity

+ API rework to align with AWS.
  This is part of an ongoing effort to conform to Amazons API and to
  move towards using boto as our client.
  https://github.com/heat-api/heat/wiki/Heat-CLI-Boto-migration-&-API-rework

+ Ubuntu 12.04 host support and Ubuntu 10.04 and 12.04 guest support.
  https://github.com/heat-api/heat/wiki/Roadmap-Feature:-Debian-Ubuntu-support

+ heat-jeos now a separate command.
  Heat JEOS image creation changed from 'heat jeos_create' to a separate
  repo and command called heat-jeos.
  https://github.com/heat-api/heat-jeos

+ Various manual pages added for heat commands.

+ Implemented describe stack resource commands.


Heat website:

http://heat-api.org/

Our mailing list:

http://lists.heat-api.org/mailman/listinfo

Download Heat API:

https://github.com/heat-api/heat/tags


___
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] Jenkins

[Joseph Suh]

Gary,

Apparently, it happened to me. Tests took 13 hours and came with failure.

Thanks,

Joseph


(w) 703-248-6160
(f) 703-812-3712
3811 N. Fairfax Drive Suite 200
Arlington, VA, 22203, USA
http://www.east.isi.edu/~jsuh

- Original Message -
From: "Gary Kotton" 
To: openstack@lists.launchpad.net
Sent: Wednesday, June 27, 2012 1:04:28 PM
Subject: [Openstack] Jenkins

Hi,
Is anyone aware of a problem with Jenkins?
Thanks
Gary

___
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] [Swift] Problem with merging

[John Postlethwait]

Jenkins has been broken since yesterday. The infrastructure team is trying to 
address that now, it will merge when it is back up. 


John Postlethwait
Nebula, Inc.
206-999-4492


On Wednesday, June 27, 2012 at 9:09 AM, Victor Rodionov wrote:

> Hello
> 
> I have patch https://review.openstack.org/#/c/7565/ (Patch for Swift 
> Solaris (illumos) compatibility), that was approved, but during merging 
> something goes wrong. It seems it's jenkins preblem, can someone whe 
> responsible for this, start merging again please.
> 
> 
> Thanks,
> Victor
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net (mailto: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] Jenkins

[Gary Kotton]

Hi,
Is anyone aware of a problem with Jenkins?
Thanks
Gary

___
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] Snapshot stuck in Queued state, no erros found in compute log

[Jay Pipes]

On 06/27/2012 12:28 PM, Leander Bessa Beernaert wrote:

You sir a my hero! I turned out someone altered the filesystem before
installing OpenStack leaving me with 3gb partition for the operating
system.


LOL, no worries. I remembered running into that in the first TryStack 
zone deployment.


Best,
-jay

___
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] Snapshot stuck in Queued state, no erros found in compute log

[Leander Bessa Beernaert]

You sir a my hero! I turned out someone altered the filesystem before
installing OpenStack leaving me with 3gb partition for the operating
system.

Thanks.
Leander

On Wed, Jun 27, 2012 at 4:32 PM, Jay Pipes  wrote:

> This looks very familiar :) Make sure that you have enough space in the
> partition that houses /tmp (usually whatever partition has / mounted). The
> snapshot operation requires at least as much space in /tmp as the size of
> the snapshot to be made.
>
> If you have improperly given yourself a very small root partition (likely
> if you are using devstack or devstack's PXE images), then you can remedy
> the situation using a bit of a hack:
>
> ln -s /tmp /some/mount/with/space
>
> Best,
> -jay
>
>
> On 06/27/2012 08:52 AM, Leander Bessa Beernaert wrote:
>
>> I've tried to snapshot again today and i found this error in the
>> compute.log:
>> http://paste.openstack.org/**show/18882/
>>
>> Any ideas?
>>
>> On Tue, Jun 26, 2012 at 9:26 AM, Leander Bessa Beernaert
>> mailto:leande...@gmail.com>> wrote:
>>
>>I can't find any error traces in the glance api and registry log.
>>
>>
>>On Mon, Jun 25, 2012 at 7:39 PM, Vishvananda Ishaya
>>mailto:vishvana...@gmail.com>**> wrote:
>>
>>Usually queued means it didn't ever get uploaded into glance.
>>Any errors in the glance log? I have never seen the error below,
>>but it could be related.
>>
>>Vish
>>
>>On Jun 25, 2012, at 3:50 AM, Leander Bessa Beernaert wrote:
>>
>> Hello,
>>>
>>>I've performed snapshots over and over without ever running
>>>into trouble, however now one of them is stuck in the Queued
>>>state. I've searched the machine's compute.log for any
>>>indication of an error, but nothing showed up. I did a quick
>>>search and usually the erros appear in the compute.log or the
>>>libivirtd.log. The only thing i found in the libvirtd.log were
>>>these two lines:
>>>
>>>2012-06-25 10:37:05.957+: 6830: warning :
>>>qemuCapsInit:856 : Failed to get host power management
>>>capabilities
>>>2012-06-25 10:37:06.612+: 6831: error :
>>>virExecWithHook:328 : Cannot find 'pm-is-supported' in
>>>path: No such file or director
>>>
>>>Could that be the problem?
>>>
>>>Regards,
>>>Leander
>>>__**_
>>>Mailing list: 
>>> https://launchpad.net/~**openstack
>>>Post to : openstack@lists.launchpad.net
>>>
>>> >> >
>>>
>>>Unsubscribe : 
>>> https://launchpad.net/~**openstack
>>>More help   : 
>>> https://help.launchpad.net/**ListHelp
>>>
>>
>>
>>
>>
>>
>> __**_
>> Mailing list: 
>> https://launchpad.net/~**openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : 
>> https://launchpad.net/~**openstack
>> More help   : 
>> https://help.launchpad.net/**ListHelp
>>
>>
>
> __**_
> Mailing list: 
> https://launchpad.net/~**openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~**openstack
> More help   : 
> https://help.launchpad.net/**ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] RFC: Thoughts on improving OpenStack GIT commit practice/history

[Vishvananda Ishaya]

On Jun 27, 2012, at 3:52 AM, Daniel P. Berrange wrote:

> The following document presented for discussion is based on my
> experiance over the past few months getting involved with OpenStack
> Nova through learning the codebase, examining its history, writing
> code and participating in reviews. I want to stress, that I don't
> intend this is a criticism of any individuals. My desire is that
> this be taken as constructive feedback to help the project as a
> whole over the long term, since I believe OpenStack can benefit
> from stricter practices commonly followed in other mainstream
> opensource projects using GIT.



Thank you for your detailed instructions and examples. I think we could
definitely could be more careful about keeping our history clean. My
general thoughts about commit messages has been that I want them to
to be concise and to the point and the details are in the  code itself. If
more information is needed then there are bug reports and review
discussions that are available.

Your points about offline browsing are well taken however, so I will
start including more details in my commit messages about the original
problem and rationale for the solution. I recommend everyone follow
suit.

Vish


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

[Openstack] [Swift] Problem with merging

[Victor Rodionov]

Hello

I have patch https://review.openstack.org/#/c/7565/ (Patch for Swift 
Solaris (illumos) compatibility), that was approved, but during merging 
something goes wrong. It seems it's jenkins preblem, can someone whe 
responsible for this, start merging again please.



Thanks,
Victor

___
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] Possible inconsistency between devstack/nova execution and test_virt_drivers.py

[Vishvananda Ishaya]

We generally add methods to the fake as they are needed by the implementation. 
You should probably add the needed methods and return fake values.

Vish

On Jun 27, 2012, at 7:17 AM, Leander Bessa Beernaert wrote:

> I've been looking at the implementation of the tests and i the fake_libvirt 
> is a bit incomplete and lacks a lot of methods. This lack of methods causes 
> my diagnostics code to fail the test since an error is produced. 
> 
> For instance this is the output from dir(virDomain) from the fake_libvirt:
> 
> ['UUIDString', 'XMLDesc', '__class__', '__delattr__', '__dict__', '__doc__', 
> '__format__', '__getattribute__', '__hash__', '__init__', '__module__', 
> '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', 
> '__sizeof__', '__str__', '__subclasshook__', '__weakref__', '_connection', 
> '_def', '_has_saved_state', '_parse_definition', '_snapshots', '_state', 
> '_transient', 'attachDevice', 'blockStats', 'create', 'createWithFlags', 
> 'destroy', 'detachDevice', 'hasManagedSaveImage', 'info', 'interfaceStats', 
> 'isActive', 'managedSave', 'managedSaveRemove', 'name', 'reset', 'resume', 
> 'shutdown', 'snapshotCreateXML', 'suspend', 'undefine']
> 
> and below from the real libvirt:
> 
> ['ID', 'OSType', 'UUID', 'UUIDString', 'XMLDesc', '__del__', '__doc__', 
> '__init__', '__module__', '_conn', '_o', 'abortJob', 'attachDevice', 
> 'attachDeviceFlags', 'autostart', 'blkioParameters', 'blockInfo', 
> 'blockIoTune', 'blockJobAbort', 'blockJobInfo', 'blockJobSetSpeed', 
> 'blockPeek', 'blockPull', 'blockResize', 'blockStats', 'blockStatsFlags', 
> 'connect', 'controlInfo', 'coreDump', 'create', 'createWithFlags', 'destroy', 
> 'destroyFlags', 'detachDevice', 'detachDeviceFlags', 'hasCurrentSnapshot', 
> 'hasManagedSaveImage', 'info', 'injectNMI', 'interfaceStats', 'isActive', 
> 'isPersistent', 'isUpdated', 'jobInfo', 'managedSave', 'managedSaveRemove', 
> 'maxMemory', 'maxVcpus', 'memoryParameters', 'memoryPeek', 'memoryStats', 
> 'migrate', 'migrate2', 'migrateGetMaxSpeed', 'migrateSetMaxDowntime', 
> 'migrateSetMaxSpeed', 'migrateToURI', 'migrateToURI2', 'name', 'openConsole', 
> 'openGraphics', 'pinVcpu', 'pinVcpuFlags', 'reboot', 'reset', 'resume', 
> 'revertToSnapshot', 'save', 'saveFlags', 'schedulerParameters', 
> 'schedulerParametersFlags', 'schedulerType', 'screenshot', 'sendKey', 
> 'setAutostart', 'setBlkioParameters', 'setBlockIoTune', 'setMaxMemory', 
> 'setMemory', 'setMemoryFlags', 'setMemoryParameters', 
> 'setSchedulerParameters', 'setSchedulerParametersFlags', 'setVcpus', 
> 'setVcpusFlags', 'shutdown', 'snapshotCreateXML', 'snapshotCurrent', 
> 'snapshotListNames', 'snapshotLookupByName', 'snapshotNum', 'state', 
> 'suspend', 'undefine', 'undefineFlags', 'updateDeviceFlags', 'vcpuPinInfo', 
> 'vcpus', 'vcpusFlags']
> 
> How do I proceed now? Should i ate the required methods to the fake_libvirt? 
> Do note that i dont have the latest libvirt installed and am therefore 
> missing another set of crucial methods which i can't test. :s
> 
> On Mon, Jun 25, 2012 at 4:43 PM, Leander Bessa Beernaert 
>  wrote:
> I've implemented a diagnostics method for libvirt. The code works perfectly 
> with the devstack installation. However, when i run the test from 
> "run_tests.sh" this happens: http://paste.openstack.org/show/18754/. >From 
> what i've been told from the irc channel, the data supplied by the test is 
> different than the one i'm currently receiving. Now, i'm unsure which data 
> type i should except from the get_diagnostics method.
> 
> 
> On Mon, Jun 25, 2012 at 4:01 PM, Sean Dague  wrote:
> On 06/25/2012 10:41 AM, Leander Bessa Beernaert wrote:
> Hello,
> 
> I'm working on the diagnostics method for libvirt. I've
> successfully managed to test it while running it manually and with
> devstack. However, the test case in test_virt_drivers.py fails since it
> supplies a different data type to the method.
> 
> Could it be possible that there's a certain mismatch between the two or
> that this particular method accepts multiple sorts of data-types?
> 
> Can you be more specific with the issue? I've been in that code recently, so 
> I might be able to help sort this out.
> 
>-Sean
> 
> -- 
> Sean Dague
> IBM Linux Technology Center
> email: sda...@linux.vnet.ibm.com
> alt-email: slda...@us.ibm.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

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

Re: [Openstack] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py

[Jay Pipes]

On 06/27/2012 10:17 AM, Leander Bessa Beernaert wrote:


How do I proceed now? Should i ate the required methods to the
fake_libvirt? Do note that i dont have the latest libvirt installed and
am therefore missing another set of crucial methods which i can't test. :s


No. In general, you only want to put methods into the fake driver that 
are *called* by the OpenStack code. If you are calling methods on the 
VirDomain with your new diagnostics code, then yes, you will need to 
implement corresponding fake methods in the fake driver.


All the best,
-jay

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

Re: [Openstack] glance access error from remote client

[Jay Pipes]

On 06/27/2012 10:04 AM, Xin Zhao wrote:

Hello,

I have an Essex install of openstack on RHEL6. The controller node has
all openstack services running, and there
are several separate compute nodes.  Now I have a problem using glance.

If I issue "glance index --host=XXX --port=9292" on the controller node,
it works fine.

If I issue the same command from a remote client node, where I have all
the relevant openstack rpms installed, it
fails with the following error message:

Failed to show index. Got error:
There was an error connecting to a server
Details: [Errno 111] Connection refused


This usually because the glance CLI tool is trying to connect to the 
localhost (which obviously isn't running the Glance API server). Have 
you looked at the difference between your OS_XXX environment variables 
between the controller node and the remote client node? It may be that 
when you are doing a glance index --host=XXX --port=9292 on the 
controller node that the glance CLI tool is actually connecting to 
localhost/127.0.0.1, but I'm not completely sure..


Best,
-jay

___
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] Snapshot stuck in Queued state, no erros found in compute log

[Jay Pipes]

This looks very familiar :) Make sure that you have enough space in the 
partition that houses /tmp (usually whatever partition has / mounted). 
The snapshot operation requires at least as much space in /tmp as the 
size of the snapshot to be made.


If you have improperly given yourself a very small root partition 
(likely if you are using devstack or devstack's PXE images), then you 
can remedy the situation using a bit of a hack:


ln -s /tmp /some/mount/with/space

Best,
-jay

On 06/27/2012 08:52 AM, Leander Bessa Beernaert wrote:

I've tried to snapshot again today and i found this error in the
compute.log:
http://paste.openstack.org/show/18882/

Any ideas?

On Tue, Jun 26, 2012 at 9:26 AM, Leander Bessa Beernaert
mailto:leande...@gmail.com>> wrote:

I can't find any error traces in the glance api and registry log.


On Mon, Jun 25, 2012 at 7:39 PM, Vishvananda Ishaya
mailto:vishvana...@gmail.com>> wrote:

Usually queued means it didn't ever get uploaded into glance.
Any errors in the glance log? I have never seen the error below,
but it could be related.

Vish

On Jun 25, 2012, at 3:50 AM, Leander Bessa Beernaert wrote:


Hello,

I've performed snapshots over and over without ever running
into trouble, however now one of them is stuck in the Queued
state. I've searched the machine's compute.log for any
indication of an error, but nothing showed up. I did a quick
search and usually the erros appear in the compute.log or the
libivirtd.log. The only thing i found in the libvirtd.log were
these two lines:

2012-06-25 10:37:05.957+: 6830: warning :
qemuCapsInit:856 : Failed to get host power management
capabilities
2012-06-25 10:37:06.612+: 6831: error :
virExecWithHook:328 : Cannot find 'pm-is-supported' in
path: No such file or director

Could that be the problem?

Regards,
Leander
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp






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




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

Re: [Openstack] create volume hangs at creating.

[Jay Pipes]

On 06/27/2012 06:45 AM, Milind wrote:

Hi,

I am still facing this problem following is the log.


I actually don't see any errors in the log file contents below (you can 
ignore the silly AssertionError thing about threading.pyc).


Perhaps you could try executing the underlying volume creation commands 
as root and see if you get any output or if things just hang? From what 
I can tell, those commands would be:


sudo lvcreate -L 1G -n volume-0001 nova-volumes
sudo tgtadm --op new --lld=iscsi --mode=target --tid=1 
--targetname=iqn.2010-10.org.openstack:volume-0001


Also remember that your nova-volumes volume group must have enough size 
in it to create this volume!


Best,
-jay


2012-06-27 16:13:10 DEBUG nova.manager [-] Running periodic task
VolumeManager._publish_service_capabilities from (pid=17850)
periodic_tasks /usr/lib/python2.7/dist-packages/nova/manager.py:152
2012-06-27 16:13:10 DEBUG nova.manager [-] Running periodic task
VolumeManager._report_driver_status from (pid=17850) periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:152
2012-06-27 16:14:10 DEBUG nova.manager [-] Running periodic task
VolumeManager._publish_service_capabilities from (pid=17850)
periodic_tasks /usr/lib/python2.7/dist-packages/nova/manager.py:152
2012-06-27 16:14:10 DEBUG nova.manager [-] Running periodic task
VolumeManager._report_driver_status from (pid=17850) periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:152
2012-06-27 16:14:36 DEBUG nova.rpc.amqp [-] received {u'_context_roles':
[u'admin'], u'_context_request_id':
u'req-07220301-c87c-40e3-a211-cc4725bcacd3', u'_context_read_deleted':
u'no', u'args': {u'volume_id': 1, u'snapshot_id': None},
u'_context_auth_token': '', u'_context_is_admin': True,
u'_context_project_id': u'68124ec3a778447093eba446aa896105',
u'_context_timestamp': u'2012-06-27T10:44:36.284391',
u'_context_user_id': u'434a94c6f63e43289702353f410ab693', u'method':
u'create_volume', u'_context_remote_address': u'10.253.59.152'} from
(pid=17850) _safe_log
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
2012-06-27 16:14:36 DEBUG nova.rpc.amqp
[req-07220301-c87c-40e3-a211-cc4725bcacd3
434a94c6f63e43289702353f410ab693 68124ec3a778447093eba446aa896105]
unpacked context: {'user_id': u'434a94c6f63e43289702353f410ab693',
'roles': [u'admin'], 'timestamp': '2012-06-27T10:44:36.284391',
'auth_token': '', 'remote_address': u'10.253.59.152',
'is_admin': True, 'request_id':
u'req-07220301-c87c-40e3-a211-cc4725bcacd3', 'project_id':
u'68124ec3a778447093eba446aa896105', 'read_deleted': u'no'} from
(pid=17850) _safe_log
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
2012-06-27 16:14:36 INFO nova.volume.manager
[req-07220301-c87c-40e3-a211-cc4725bcacd3
434a94c6f63e43289702353f410ab693 68124ec3a778447093eba446aa896105]
volume volume-0001: creating
2012-06-27 16:14:36 DEBUG nova.volume.manager
[req-07220301-c87c-40e3-a211-cc4725bcacd3
434a94c6f63e43289702353f410ab693 68124ec3a778447093eba446aa896105]
volume volume-0001: creating lv of size 1G from (pid=17850)
create_volume /usr/lib/python2.7/dist-packages/nova/volume/manager.py:120
2012-06-27 16:14:36 DEBUG nova.utils
[req-07220301-c87c-40e3-a211-cc4725bcacd3
434a94c6f63e43289702353f410ab693 68124ec3a778447093eba446aa896105]
Running cmd (subprocess): sudo nova-rootwrap lvcreate -L 1G -n
volume-0001 nova-volumes from (pid=17850) execute
/usr/lib/python2.7/dist-packages/nova/utils.py:219
Exception AssertionError: AssertionError() in  ignored
2012-06-27 16:14:36 DEBUG nova.volume.manager
[req-07220301-c87c-40e3-a211-cc4725bcacd3
434a94c6f63e43289702353f410ab693 68124ec3a778447093eba446aa896105]
volume volume-0001: creating export from (pid=17850) create_volume
/usr/lib/python2.7/dist-packages/nova/volume/manager.py:131
2012-06-27 16:14:41 DEBUG nova.utils
[req-07220301-c87c-40e3-a211-cc4725bcacd3
434a94c6f63e43289702353f410ab693 68124ec3a778447093eba446aa896105]
Running cmd (subprocess): sudo nova-rootwrap tgtadm --op new --lld=iscsi
--mode=target --tid=1
--targetname=iqn.2010-10.org.openstack:volume-0001 from (pid=17850)
execute /usr/lib/python2.7/dist-packages/nova/utils.py:219
Exception AssertionError: AssertionError() in  ignored



Regards,
Milind


___
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] horizon install from devstack fails to find glanceclient/versioninfo

[Doug Hellmann]

On Wed, Jun 27, 2012 at 9:44 AM, Doug Hellmann
wrote:

>
>
> On Wed, Jun 27, 2012 at 8:23 AM, Doug Hellmann <
> doug.hellm...@dreamhost.com> wrote:
>
>>
>>
>> On Tue, Jun 26, 2012 at 8:14 PM, Dean Troyer  wrote:
>>
>>> On Tue, Jun 26, 2012 at 6:37 PM, Doug Hellmann
>>>  wrote:
>>> > OK, I got past that part but now I'm seeing an error about a missing
>>> volume
>>> > group "stack-volumes". Is that related to enabling cinder? The only
>>> settings
>>> > I have in my localrc file are passwords. Is there something else I
>>> need to
>>> > do to ensure cinder is "on"?
>>>
>>> I use this to enable cinder:
>>>
>>> ENABLED_SERVICES=$(echo $ENABLED_SERVICES | sed
>>> 's/n-vol/c-api,c-sch,c-vol/')
>>>
>>> But the volume group should be created either way.  The cinder patch
>>> did change its name from nova-volumes to stack-volumes though.
>>>
>>
>> I'm not doing anything that makes me care which volume storage I'm using,
>> so I don't necessarily need to enable cinder. For whatever reason, with the
>> defaults, the volume group isn't being created (or has the wrong name). I'm
>> using a fresh vagrant VM with all of my sandboxes updated to HEAD this
>> morning.
>>
>> I'll run it again and get a list of the volume groups that do exist and
>> see if I can figure out what's going wrong.
>>
>
> It looks like a problem creating the volume group on the loopback device.
> I get:
>
> Device /dev/loop0 not found (or ignored by filtering).
> Unable to add physical volume '/dev/loop0' to volume group
> 'stack-volumes'.
>
> This is on Ubuntu Precise. It was working Monday in the same image.
>

Deleting the existing backing file and letting devstack re-create it fixed
the problem. I've never had to do that before, so I have no idea what might
have caused it to be necessary this time.

Doug
___
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] Possible inconsistency between devstack/nova execution and test_virt_drivers.py

[Leander Bessa Beernaert]

I've been looking at the implementation of the tests and i the fake_libvirt
is a bit incomplete and lacks a lot of methods. This lack of methods causes
my diagnostics code to fail the test since an error is produced.

For instance this is the output from dir(virDomain) from the fake_libvirt:

['UUIDString', 'XMLDesc', '__class__', '__delattr__', '__dict__',
> '__doc__', '__format__', '__getattribute__', '__hash__', '__init__',
> '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__',
> '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__',
> '_connection', '_def', '_has_saved_state', '_parse_definition',
> '_snapshots', '_state', '_transient', 'attachDevice', 'blockStats',
> 'create', 'createWithFlags', 'destroy', 'detachDevice',
> 'hasManagedSaveImage', 'info', 'interfaceStats', 'isActive', 'managedSave',
> 'managedSaveRemove', 'name', 'reset', 'resume', 'shutdown',
> 'snapshotCreateXML', 'suspend', 'undefine']


and below from the real libvirt:

['ID', 'OSType', 'UUID', 'UUIDString', 'XMLDesc', '__del__', '__doc__',
> '__init__', '__module__', '_conn', '_o', 'abortJob', 'attachDevice',
> 'attachDeviceFlags', 'autostart', 'blkioParameters', 'blockInfo',
> 'blockIoTune', 'blockJobAbort', 'blockJobInfo', 'blockJobSetSpeed',
> 'blockPeek', 'blockPull', 'blockResize', 'blockStats', 'blockStatsFlags',
> 'connect', 'controlInfo', 'coreDump', 'create', 'createWithFlags',
> 'destroy', 'destroyFlags', 'detachDevice', 'detachDeviceFlags',
> 'hasCurrentSnapshot', 'hasManagedSaveImage', 'info', 'injectNMI',
> 'interfaceStats', 'isActive', 'isPersistent', 'isUpdated', 'jobInfo',
> 'managedSave', 'managedSaveRemove', 'maxMemory', 'maxVcpus',
> 'memoryParameters', 'memoryPeek', 'memoryStats', 'migrate', 'migrate2',
> 'migrateGetMaxSpeed', 'migrateSetMaxDowntime', 'migrateSetMaxSpeed',
> 'migrateToURI', 'migrateToURI2', 'name', 'openConsole', 'openGraphics',
> 'pinVcpu', 'pinVcpuFlags', 'reboot', 'reset', 'resume', 'revertToSnapshot',
> 'save', 'saveFlags', 'schedulerParameters', 'schedulerParametersFlags',
> 'schedulerType', 'screenshot', 'sendKey', 'setAutostart',
> 'setBlkioParameters', 'setBlockIoTune', 'setMaxMemory', 'setMemory',
> 'setMemoryFlags', 'setMemoryParameters', 'setSchedulerParameters',
> 'setSchedulerParametersFlags', 'setVcpus', 'setVcpusFlags', 'shutdown',
> 'snapshotCreateXML', 'snapshotCurrent', 'snapshotListNames',
> 'snapshotLookupByName', 'snapshotNum', 'state', 'suspend', 'undefine',
> 'undefineFlags', 'updateDeviceFlags', 'vcpuPinInfo', 'vcpus', 'vcpusFlags']


How do I proceed now? Should i ate the required methods to the
fake_libvirt? Do note that i dont have the latest libvirt installed and am
therefore missing another set of crucial methods which i can't test. :s

On Mon, Jun 25, 2012 at 4:43 PM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> I've implemented a diagnostics method for libvirt. The code works
> perfectly with the devstack installation. However, when i run the test from
> "run_tests.sh" this happens: http://paste.openstack.org/show/18754/. From
> what i've been told from the irc channel, the data supplied by the test is
> different than the one i'm currently receiving. Now, i'm unsure which data
> type i should except from the get_diagnostics method.
>
>
> On Mon, Jun 25, 2012 at 4:01 PM, Sean Dague wrote:
>
>> On 06/25/2012 10:41 AM, Leander Bessa Beernaert wrote:
>>
>>> Hello,
>>>
>>> I'm working on the diagnostics method for libvirt. I've
>>> successfully managed to test it while running it manually and with
>>> devstack. However, the test case in test_virt_drivers.py fails since it
>>> supplies a different data type to the method.
>>>
>>> Could it be possible that there's a certain mismatch between the two or
>>> that this particular method accepts multiple sorts of data-types?
>>>
>>
>> Can you be more specific with the issue? I've been in that code recently,
>> so I might be able to help sort this out.
>>
>>-Sean
>>
>> --
>> Sean Dague
>> IBM Linux Technology Center
>> email: sda...@linux.vnet.ibm.com
>> alt-email: slda...@us.ibm.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

[Openstack] [metering] integrating Quantum and Ceilometer

[Doug Hellmann]

Hello,

As part of the ceilometer project¹, we're working on retrieving usage
data from various OpenStack components. We would like to integrate
with Quantum for information about network resource utilization that a
deployer might want to bill their tenants for.

Ceilometer has a plugin-based architecture, which makes it easy to add
new measurement types and data collectors. Our approach with other
measurements is to collect everything and let the ceilometer user decide
what to bill for and what to ignore (they can turn off measurements for
things they do not care about).

Depending on the project and the type of data, we can either
use the notification events generated by allocating/deallocating
a resource, or we can poll for metrics being collected elsewhere.
We will probably want to use both approaches for integrating
with Quantum (e.g., use events for things like IP allocation and
polling for I/O).

Do you have any advice on how to integrate Ceilometer and Quantum?
For example, does Quantum emit notifications and does it collect
(or provide an API to query) I/O statistics?

Thanks,
Doug


¹  http://launchpad.net/ceilometer
___
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] need help on swift and python

[Yogesh Bansal]

Hi Chmouel,

I am using window machine for my developemt. I have install the
python-cloudfiles and can see in the python path. But still I am unable to
import the cloudfiles into my code.


Can you suggest where I am doing any mistake.





Thanks & Regards
Yogesh Bansal

-Original Message-
From: Chmouel Boudjnah [mailto:chmo...@chmouel.com] 
Sent: 27 June 2012 AM 1:50
To: Christophe Le Guern
Cc: Yogesh Bansal; openstack@lists.launchpad.net
Subject: Re: [Openstack] need help on swift and python

Yogesh,

a couple of years ago I wrote some simple cloudfiles functions that uses
python-cloudfiles to do some common task which you may want to look at to
see how it's done, available here :

https://github.com/chmouel/cloud-files-helper

Chmouel

On Tue, Jun 26, 2012 at 8:31 AM, Christophe Le Guern 
wrote:
> Hi Yogesh,
>
> Here is an example using swauth middleware and swift:
>
> **
> from cloudfiles.connection import Connection
>
> conn = Connection("account:user", "password",
> authurl="https://SWIFT-URL/auth/v1.0";)
>
> container = conn.create_container("mycontainer")
>
> obj = container.create_object("myobject.txt")
> obj.content_type = "text/plain"
> obj.write("Hello World")
> **
>
> Christophe
>
> On Tue, Jun 26, 2012 at 7:14 AM, Yogesh Bansal 
wrote:
>> Hi,
>>
>>
>>
>> I want to upload a file or image on swift object storage server.  I 
>> can do it using curl command. But I am not able to do it using python 
>> apis. I am using Django and python to make web based application, 
>> which required to store file from client to swift object storage server.
>>
>>
>>
>> Is there any swift  and python experts, who can guide me in this regard.
>>
>>
>>
>> I am able to create and list containers using python.
>>
>>
>>
>> An example will be very helpful.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks
>>
>> Yogesh Bansal
>>
>>
>>
>>
>> ___
>> 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

[Openstack] glance access error from remote client

[Xin Zhao]

Hello,

I have an Essex install of openstack on RHEL6. The controller node has 
all openstack services running, and there

are several separate compute nodes.  Now I have a problem using glance.

If I issue "glance index --host=XXX --port=9292" on the controller node, 
it works fine.


If I issue the same command from a remote client node, where I have all 
the relevant openstack rpms installed, it

fails with the following error message:

Failed to show index. Got error:
There was an error connecting to a server
Details: [Errno 111] Connection refused

On the same client node, I can query images and instances using 
euca2ools, they just work fine. And I also can telnet

to the 9292 port on the controller node from the client side.

In both cases, I use the credentials of the admin account.

Any wisdom on what could cause this problem?

Thanks,
Xin



smime.p7s
Description: S/MIME Cryptographic Signature
___
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] horizon install from devstack fails to find glanceclient/versioninfo

[Doug Hellmann]

On Wed, Jun 27, 2012 at 8:23 AM, Doug Hellmann
wrote:

>
>
> On Tue, Jun 26, 2012 at 8:14 PM, Dean Troyer  wrote:
>
>> On Tue, Jun 26, 2012 at 6:37 PM, Doug Hellmann
>>  wrote:
>> > OK, I got past that part but now I'm seeing an error about a missing
>> volume
>> > group "stack-volumes". Is that related to enabling cinder? The only
>> settings
>> > I have in my localrc file are passwords. Is there something else I need
>> to
>> > do to ensure cinder is "on"?
>>
>> I use this to enable cinder:
>>
>> ENABLED_SERVICES=$(echo $ENABLED_SERVICES | sed
>> 's/n-vol/c-api,c-sch,c-vol/')
>>
>> But the volume group should be created either way.  The cinder patch
>> did change its name from nova-volumes to stack-volumes though.
>>
>
> I'm not doing anything that makes me care which volume storage I'm using,
> so I don't necessarily need to enable cinder. For whatever reason, with the
> defaults, the volume group isn't being created (or has the wrong name). I'm
> using a fresh vagrant VM with all of my sandboxes updated to HEAD this
> morning.
>
> I'll run it again and get a list of the volume groups that do exist and
> see if I can figure out what's going wrong.
>

It looks like a problem creating the volume group on the loopback device. I
get:

Device /dev/loop0 not found (or ignored by filtering).
Unable to add physical volume '/dev/loop0' to volume group
'stack-volumes'.

This is on Ubuntu Precise. It was working Monday in the same image.

Doug
___
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] RFC: Thoughts on improving OpenStack GIT commit practice/history

[Daniel P. Berrange]

On Wed, Jun 27, 2012 at 03:24:21PM +0200, Vincent Untz wrote:
> Hi,
> 
> As a recent contributor to OpenStack, but with experience in other
> projects, I think moving in the directions you document would be good.
> And as you wrote, it's common practice in many many projects, which is
> another argument for this :-)
> 
> However, one comment:
> 
> Le mercredi 27 juin 2012, à 11:52 +0100, Daniel P. Berrange a écrit :
> > It might be mentioned that Gerrit's handling of patch series is not entirely
> > perfect. This is a not a valid reason to avoid creating patch series.
> 
> It'd be really great if we could first improve Gerrit to handle the
> patch series workflow in a better way. Without such a change, pushing
> patch series to Gerrit is really no fun for anyone :/
> 
> I've no idea if this is currently being worked on (at least, I don't
> really se an issue reported in Gerrit's issue tracker). Maybe we should
> sit down and at least document how we'd like to improve this specific
> workflow?

Yep, no argument that Gerrit could do with some improvements, but having
submitted a number of non-trivial patch series to Nova, I don't think
current Gerrit UI is a complete blocker to adoption. It is not ideal,
but it isn't too painful if you're aware of what to look for. I think
the main problem is that since the patch dependancies are not obvious
in the UI, reviewers tend to miss the fact that they're reviewing a
patch that's part of a series.

I submitted one bug against Gerrit already to improve the way it
deals with bug resolution wrt patch series

  https://bugs.launchpad.net/openstack-ci/+bug/1018013

One think people might not be aware of is that if you create a patch
series on a branch and push that branch using 'git review', then the
branch name becomes the Gerrit topic which provides an easy way to
see the entire series. Alternatively the blueprint or bug IDs might
be chosen to form the topic. For example my most recent series:

https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bug/1003373,n,z


I think the main patch display UI though needs to make it much more
obvious that a particular patch is part of a series so that reviewers
know to review the work as a whole. The UI does display dependencies.
eg see the "depends on" and "needed by" links:

  https://review.openstack.org/#/c/8694/

but I'd suggest that UI be changed so that instead of showing only the
previous and next, it displays all patches in the series at once.

Gerrit could also be less stupid about repeatedly trying & failing to
merge a patch due to missing dependent patches. In fact I'll file a
bug about that flaw now too.

Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

___
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] RFC: Thoughts on improving OpenStack GIT commit practice/history

[Vincent Untz]

Hi,

As a recent contributor to OpenStack, but with experience in other
projects, I think moving in the directions you document would be good.
And as you wrote, it's common practice in many many projects, which is
another argument for this :-)

However, one comment:

Le mercredi 27 juin 2012, à 11:52 +0100, Daniel P. Berrange a écrit :
> It might be mentioned that Gerrit's handling of patch series is not entirely
> perfect. This is a not a valid reason to avoid creating patch series.

It'd be really great if we could first improve Gerrit to handle the
patch series workflow in a better way. Without such a change, pushing
patch series to Gerrit is really no fun for anyone :/

I've no idea if this is currently being worked on (at least, I don't
really se an issue reported in Gerrit's issue tracker). Maybe we should
sit down and at least document how we'd like to improve this specific
workflow?

Cheers,

Vincent

-- 
Les gens heureux ne sont pas pressés.

___
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] Snapshot stuck in Queued state, no erros found in compute log

[Leander Bessa Beernaert]

I've tried to snapshot again today and i found this error in the
compute.log:
http://paste.openstack.org/show/18882/

Any ideas?

On Tue, Jun 26, 2012 at 9:26 AM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> I can't find any error traces in the glance api and registry log.
>
>
> On Mon, Jun 25, 2012 at 7:39 PM, Vishvananda Ishaya  > wrote:
>
>> Usually queued means it didn't ever get uploaded into glance. Any errors
>> in the glance log? I have never seen the error below, but it could be
>> related.
>>
>> Vish
>>
>> On Jun 25, 2012, at 3:50 AM, Leander Bessa Beernaert wrote:
>>
>> Hello,
>>
>> I've performed snapshots over and over without ever running into trouble,
>> however now one of them is stuck in the Queued state. I've searched the
>> machine's compute.log for any indication of an error, but nothing showed
>> up. I did a quick search and usually the erros appear in the compute.log or
>> the libivirtd.log. The only thing i found in the libvirtd.log were these
>> two lines:
>>
>> 2012-06-25 10:37:05.957+: 6830: warning : qemuCapsInit:856 : Failed
>>> to get host power management capabilities
>>> 2012-06-25 10:37:06.612+: 6831: error : virExecWithHook:328 : Cannot
>>> find 'pm-is-supported' in path: No such file or director
>>
>>
>> Could that be the problem?
>>
>>  Regards,
>> Leander
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] horizon install from devstack fails to find glanceclient/versioninfo

[Doug Hellmann]

On Tue, Jun 26, 2012 at 8:14 PM, Dean Troyer  wrote:

> On Tue, Jun 26, 2012 at 6:37 PM, Doug Hellmann
>  wrote:
> > OK, I got past that part but now I'm seeing an error about a missing
> volume
> > group "stack-volumes". Is that related to enabling cinder? The only
> settings
> > I have in my localrc file are passwords. Is there something else I need
> to
> > do to ensure cinder is "on"?
>
> I use this to enable cinder:
>
> ENABLED_SERVICES=$(echo $ENABLED_SERVICES | sed
> 's/n-vol/c-api,c-sch,c-vol/')
>
> But the volume group should be created either way.  The cinder patch
> did change its name from nova-volumes to stack-volumes though.
>

I'm not doing anything that makes me care which volume storage I'm using,
so I don't necessarily need to enable cinder. For whatever reason, with the
defaults, the volume group isn't being created (or has the wrong name). I'm
using a fresh vagrant VM with all of my sandboxes updated to HEAD this
morning.

I'll run it again and get a list of the volume groups that do exist and see
if I can figure out what's going wrong.


>
> dt
>
> --
>
> Dean Troyer
> dtro...@gmail.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] [metering] Meeting agenda for Thursday at 16:00 UTC (June 28th, 2012)

[Julien Danjou]

Hi,

The metering project team holds a meeting in #openstack-meeting,
Thursdays at 1600 UTC
.

Everyone is welcome.

Agenda:
http://wiki.openstack.org/Meetings/MeteringAgenda

  * Review last week's actions
  * Discuss and vote the incubation application proposal to be submitted
to PPB
http://wiki.openstack.org/Projects/IncubatorApplicationCeilometer
  * Open discussion

Cheers,
-- 
   Julien


pgp9BgeJq4JkS.pgp
Description: PGP signature
___
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] how to add python-quantumclient dependency into nova/tools/test-requires

[Yong Sheng Gong]

 Hi,I am implementing the nova network api call to quantum API 2.0.  The new nova network api for quantum will use python-quantumclient to call Quantum API 2.0.The test cases need add python-quantumclient dependency into nova/tools/tests-requires.Who can tell me how to write?ThanksYong Sheng Gong

___
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] instances loosing IP address while running, due to No DHCPOFFER

[Tom Sante]

Hey,

I seem to have the same issue with our VMs, I commented (comment #7) on a bug 
report that seems to correspond with our DHCP issues: 
https://bugs.launchpad.net/nova/+bug/887162

Please report if you are still affected by this issue on the bug page so the 
developers can look into a fix.

Regards,


Op zaterdag 16 juni 2012, om 01:19 heeft Christian Parpart het volgende 
geschreven:

> Hey all,
> 
> it now just happened twice again, both just today. and the last at 22:00 UTC, 
> with
> the following in the nova-network's syslog:
> 
> root@gw1:/var/log# grep 'dnsmasq.*10889' daemon.log 
> Jun 15 17:39:32 cesar1 dnsmasq[10889]: started, version v2.62-7-g4ce4f37 
> cachesize 150
> Jun 15 17:39:32 cesar1 dnsmasq[10889]: compile time options: IPv6 GNU-getopt 
> no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
> Jun 15 17:39:32 cesar1 dnsmasq-dhcp[10889]: DHCP, static leases only on 
> 10.10.40.3, lease time 3d
> Jun 15 17:39:32 cesar1 dnsmasq[10889]: reading /etc/resolv.conf
> Jun 15 17:39:32 cesar1 dnsmasq[10889]: using nameserver 4.2.2.1#53
> Jun 15 17:39:32 cesar1 dnsmasq[10889]: using nameserver 178.63.26.173#53
> Jun 15 17:39:32 cesar1 dnsmasq[10889]: using nameserver 192.168.2.122#53
> Jun 15 17:39:32 cesar1 dnsmasq[10889]: using nameserver 192.168.2.121#53
> Jun 15 17:39:32 cesar1 dnsmasq[10889]: read /etc/hosts - 519 addresses
> Jun 15 17:39:32 cesar1 dnsmasq-dhcp[10889]: read 
> /var/lib/nova/networks/nova-br100.conf
> Jun 15 21:59:41 cesar1 dnsmasq-dhcp[10889]: DHCPREQUEST(br100) 10.10.40.16 
> fa:16:3e:3d:ff:f3 
> Jun 15 21:59:41 cesar1 dnsmasq-dhcp[10889]: DHCPACK(br100) 10.10.40.16 
> fa:16:3e:3d:ff:f3 redis-appdata1
> 
> it seemed that this once VM was the only one who sent a dhcp request over the 
> past 5 hours, 
> and that first wone got replied with dhcp ack, and that is it.
> That's been the time the host behind that IP (redis-appdata1) stopped 
> functioning.
> 
> However, I now actually did update dnsmasq on our gateway note, to latest 
> trunk 
> of dnsmasq git repository, killed dnsmasq, restarted nova-network (which 
> auto-starts dnsmasq per 
> device).
> 
> Now, I really hoped that this one particular bug fix was the cause of the 
> downtime, 
> but appearently, thet MIGHT be another factor.
> 
> There is unfortunately nothing to read in the VM's syslog.
> What else could cause the VM to forget its IP?
> Can this also be caused by send_arp_for_ha=True?
> 
> Regards,
> Christian.
> 
> Christian.
> On Fri, Jun 15, 2012 at 2:50 AM, Nathanael Burton 
> mailto:nathanael.i.bur...@gmail.com)> wrote:
> > FWIW I haven't run across the dnsmasq bug in our environment using EPEL 
> > packages. 
> > Nate
> > On Jun 14, 2012 7:20 PM, "Vishvananda Ishaya"  > (mailto:vishvana...@gmail.com)> wrote:
> > > Are you running in VLAN mode? If so, you probably need to update to a new 
> > > version of dnsmasq. See this message for reference:
> > > 
> > > http://osdir.com/ml/openstack-cloud-computing/2012-05/msg00785.html 
> > > 
> > > Vish
> > > 
> > > On Jun 14, 2012, at 1:41 PM, Christian Parpart wrote:
> > > > Hey all,
> > > > 
> > > > I feel really sad with saying this, now, that we have quite a few 
> > > > instances in producgtion 
> > > > since about 5 days at least, I now have encountered the second instance 
> > > > loosing its
> > > > IP address due to "No DHCPOFFER" (as of syslog in the instance).
> > > > 
> > > > I checked the logs in the central nova-network and gateway node and 
> > > > found
> > > > dnsmasq still to reply on requests from all the other instances and it 
> > > > even
> > > > got the request from the instance in question and even sent an OFFER, 
> > > > as of what
> > > > I can tell by now (i'm investigating / posting logs asap), but while it 
> > > > seemed
> > > > that the dnsmasq sends an offer, the instances says it didn't receive 
> > > > one - wtf?
> > > > 
> > > > Please tell me what I can do to actually *fix* this issue, since this 
> > > > is by far very fatal.
> > > > 
> > > > One chance I'd see (as a workaround) is, to let created instanced 
> > > > retrieve 
> > > > its IP via dhcp, but then reconfigure /etc/network/instances to 
> > > > continue with
> > > > static networking setup. However, I'd just like the dhcp thingy to get 
> > > > fixed.
> > > > 
> > > > I'm very open to any kind of helping comments, :) 
> > > > 
> > > > So long,
> > > > Christian.
> > > > 
> > > > ___
> > > > Mailing list: https://launchpad.net/~openstack
> > > > Post to : openstack@lists.launchpad.net 
> > > > (mailto: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 
> > > (mailto:openstack@lists.launchpad.net)
> > > Unsubscribe : https://launchpad.net/~openstack
> > > M

[Openstack] RFC: Thoughts on improving OpenStack GIT commit practice/history

[Daniel P. Berrange]

The following document presented for discussion is based on my
experiance over the past few months getting involved with OpenStack
Nova through learning the codebase, examining its history, writing
code and participating in reviews. I want to stress, that I don't
intend this is a criticism of any individuals. My desire is that
this be taken as constructive feedback to help the project as a
whole over the long term, since I believe OpenStack can benefit
from stricter practices commonly followed in other mainstream
opensource projects using GIT.

Enjoy the rather long doc that follows

GIT Commit Good Practice


The following document is based on experiance doing code development,
bug troubleshooting and code review across a number of projects using
GIT, including libvirt, QEMU and OpenStack Nova. Examination of other
open source projects such as the Kernel, CoreUtils, GNULIB and more
suggested they all follow a fairly common practice. It is motivated by
a desire to improve the quality of the Nova GIT history. Quality is
a hard term to define in computing; One man's "Thing of Beauty" is
another's man's "Evil Hack". We can, however, come up with some general
guidelines for what todo, or conversely what not todo, when publishing
GIT commits for merge with a project, in this case, OpenStack.

This topic can be split into two areas of concern

  1. The structured set/split of the code changes
  2. The information provided in the commit message

Executive Summary
=

The points and examples that will be raised in this document ought clearly
demonstrate the value in splitting up changes into a sequence of individual
commits, and the importance in writing good commit messages to go along
with them. If these guidelines were widely applied it would result in a
significant improvement in the quality of the OpenStack GIT history. Both
a carrot & stick will be required to effect changes. This document intends
to be the carrot by alerting people to the benefits, while anyone doing
Gerrit code review can act as the stick ;-P

In other words, when reviewing a change in Gerrit, do not simply look at
the correctness of the code. Review the commit message itself and request
improvements to its content. Look out for commits which are mixing multiple
logical changes and require the submitter to split them into separate commits.
Ensure whitespace changes are not mixed in with functional changes. Ensure
no-op code refactoring is done separately from functional changes. And so
on.

It might be mentioned that Gerrit's handling of patch series is not entirely
perfect. This is a not a valid reason to avoid creating patch series. The
tools being used should be subservient to developers needs, and since they
are open source they can be fixed / improved. Software source code is
"read mostly, write occassionally" and thus the most important criteria
is the improve the long term maintainability by the large pool of developers
in the community, and not to sacrifice too much for the sake of the single
author who may never touch the code again.

And now the long detailed guidelines & examples of good & bad practice

Structural split of changes
===

The cardinal rule for creating good commits is to ensure there is only
one "logical change" per commit. There are many reasons why this is an
important rule:

 * The smaller the amount of code being changed, the quicker & easier
   it to review & identify potential flaws.

 * If a change is found to be flawed later, it make be neccessary to
   revert the broken commit. This is much easier todo if there are
   not other unrelated code changes entangled with the original commit.

 * When troubleshooting problems using GIT's bisect capability, small
   well defined changes will aid in isolating exactly where the code
   problem was introduced.

 * When browsing history using GIT annotate/blame, small well defined
   changes also aid in isolating exactly where & why a piece of code
   came from.

Things to avoid when creating commits
-

With that in mind, there are some commonly encountered examples of
bad things to avoid

 * Mixing whitespace changes with functional code changes

   The whitespace changes will obscure the important functional
   changes, making it harder for a reviewer to correctly determine
   whether the change is correct.

   Solution: Create 2 commits, one with the whitespace changes, one
 with the functional changes. Typically the whitespace
 change would be done first, but that need not be a hard
 rule.


 * Mixing two unrelated functional changes

   Again the reviewer will find it harder to identify flaws if two
   unrelated changes are mixed together. If it becomes neccessary to
   later revert a broken commit the two unrelated changes will need to
   be untangled, with further risk of bug creation.


 * Sending large new 

[Openstack] create volume hangs at creating.

[Milind]

Hi,

I am still facing this problem following is the log.


2012-06-27 16:13:10 DEBUG nova.manager [-] Running periodic task
VolumeManager._publish_service_capabilities from (pid=17850) periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:152
2012-06-27 16:13:10 DEBUG nova.manager [-] Running periodic task
VolumeManager._report_driver_status from (pid=17850) periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:152
2012-06-27 16:14:10 DEBUG nova.manager [-] Running periodic task
VolumeManager._publish_service_capabilities from (pid=17850) periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:152
2012-06-27 16:14:10 DEBUG nova.manager [-] Running periodic task
VolumeManager._report_driver_status from (pid=17850) periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:152
2012-06-27 16:14:36 DEBUG nova.rpc.amqp [-] received {u'_context_roles':
[u'admin'], u'_context_request_id':
u'req-07220301-c87c-40e3-a211-cc4725bcacd3', u'_context_read_deleted':
u'no', u'args': {u'volume_id': 1, u'snapshot_id': None},
u'_context_auth_token': '', u'_context_is_admin': True,
u'_context_project_id': u'68124ec3a778447093eba446aa896105',
u'_context_timestamp': u'2012-06-27T10:44:36.284391', u'_context_user_id':
u'434a94c6f63e43289702353f410ab693', u'method': u'create_volume',
u'_context_remote_address': u'10.253.59.152'} from (pid=17850) _safe_log
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
2012-06-27 16:14:36 DEBUG nova.rpc.amqp
[req-07220301-c87c-40e3-a211-cc4725bcacd3 434a94c6f63e43289702353f410ab693
68124ec3a778447093eba446aa896105] unpacked context: {'user_id':
u'434a94c6f63e43289702353f410ab693', 'roles': [u'admin'], 'timestamp':
'2012-06-27T10:44:36.284391', 'auth_token': '',
'remote_address': u'10.253.59.152', 'is_admin': True, 'request_id':
u'req-07220301-c87c-40e3-a211-cc4725bcacd3', 'project_id':
u'68124ec3a778447093eba446aa896105', 'read_deleted': u'no'} from
(pid=17850) _safe_log
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
2012-06-27 16:14:36 INFO nova.volume.manager
[req-07220301-c87c-40e3-a211-cc4725bcacd3 434a94c6f63e43289702353f410ab693
68124ec3a778447093eba446aa896105] volume volume-0001: creating
2012-06-27 16:14:36 DEBUG nova.volume.manager
[req-07220301-c87c-40e3-a211-cc4725bcacd3 434a94c6f63e43289702353f410ab693
68124ec3a778447093eba446aa896105] volume volume-0001: creating lv of
size 1G from (pid=17850) create_volume
/usr/lib/python2.7/dist-packages/nova/volume/manager.py:120
2012-06-27 16:14:36 DEBUG nova.utils
[req-07220301-c87c-40e3-a211-cc4725bcacd3 434a94c6f63e43289702353f410ab693
68124ec3a778447093eba446aa896105] Running cmd (subprocess): sudo
nova-rootwrap lvcreate -L 1G -n volume-0001 nova-volumes from
(pid=17850) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219
Exception AssertionError: AssertionError() in  ignored
2012-06-27 16:14:36 DEBUG nova.volume.manager
[req-07220301-c87c-40e3-a211-cc4725bcacd3 434a94c6f63e43289702353f410ab693
68124ec3a778447093eba446aa896105] volume volume-0001: creating export
from (pid=17850) create_volume
/usr/lib/python2.7/dist-packages/nova/volume/manager.py:131
2012-06-27 16:14:41 DEBUG nova.utils
[req-07220301-c87c-40e3-a211-cc4725bcacd3 434a94c6f63e43289702353f410ab693
68124ec3a778447093eba446aa896105] Running cmd (subprocess): sudo
nova-rootwrap tgtadm --op new --lld=iscsi --mode=target --tid=1
--targetname=iqn.2010-10.org.openstack:volume-0001 from (pid=17850)
execute /usr/lib/python2.7/dist-packages/nova/utils.py:219
Exception AssertionError: AssertionError() in  ignored



Regards,
Milind
___
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] [Metering] First draft of plugin/agent documentation

[Nick Barcet]

I've just committed a first of the plugin/agent documentation to
stackforge/ceilometer.  Reviews welcome:

https://review.stackforge.org/#/c/250/

Thanks,
Nick



signature.asc
Description: OpenPGP digital signature
___
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] need help on swift and python

[Chmouel Boudjnah]

Yogesh,

a couple of years ago I wrote some simple cloudfiles functions that
uses python-cloudfiles to do some common task which you may want to
look at to see how it's done, available here :

https://github.com/chmouel/cloud-files-helper

Chmouel

On Tue, Jun 26, 2012 at 8:31 AM, Christophe Le Guern  wrote:
> Hi Yogesh,
>
> Here is an example using swauth middleware and swift:
>
> **
> from cloudfiles.connection import Connection
>
> conn = Connection("account:user", "password",
> authurl="https://SWIFT-URL/auth/v1.0";)
>
> container = conn.create_container("mycontainer")
>
> obj = container.create_object("myobject.txt")
> obj.content_type = "text/plain"
> obj.write("Hello World")
> **
>
> Christophe
>
> On Tue, Jun 26, 2012 at 7:14 AM, Yogesh Bansal  
> wrote:
>> Hi,
>>
>>
>>
>> I want to upload a file or image on swift object storage server.  I can do
>> it using curl command. But I am not able to do it using python apis. I am
>> using Django and python to make web based application, which required to
>> store file from client to swift object storage server.
>>
>>
>>
>> Is there any swift  and python experts, who can guide me in this regard.
>>
>>
>>
>> I am able to create and list containers using python.
>>
>>
>>
>> An example will be very helpful.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks
>>
>> Yogesh Bansal
>>
>>
>>
>>
>> ___
>> 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] [keystone] proposing adding Adam Young (ayoung) to keystone-core

[Syed Armani]

Adam is a great guy, He is always there if you need any help or guidance.
His work is incredible.

Best!
Syed

On Wed, Jun 27, 2012 at 12:57 PM, Razique Mahroua  wrote:

> Not part of that group, but Adam's work is indeed fantastic
>
> *Nuage & Co - Razique Mahroua** *
> razique.mahr...@gmail.com
>
>
> Le 26 juin 2012 à 23:06, Joseph Heck a écrit :
>
> Given his work in Keystone since the redux, I would like propose Adam
> Young (ayoung) be added to the group keystone-core.
>
> For a process in doing this, I thought we'd generally follow Nova's
> core-promotion process = lazy consensus over a week, and assuming no -1's
> and at least two +1's from current core members, it's good to go.
>
> -joe
>
>
>
> ___
> 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] [keystone] proposing adding Adam Young (ayoung) to keystone-core

[Razique Mahroua]

Not part of that group, but Adam's work is indeed fantastic
Nuage & Co - Razique Mahroua razique.mahr...@gmail.com

Le 26 juin 2012 à 23:06, Joseph Heck a écrit :Given his work in Keystone since the redux, I would like propose Adam Young (ayoung) be added to the group keystone-core.For a process in doing this, I thought we'd generally follow Nova's core-promotion process = lazy consensus over a week, and assuming no -1's and at least two +1's from current core members, it's good to go.-joe___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore 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